RAN2#115-e

2.1	Approval of the agenda
R2-2106900	Agenda for RAN2#115-e	Chairman
2.2	Approval of the report of the previous meeting
R2-2106901	RAN2#114-e Meeting Report	MCC
2.4	Others
R2-2108870	Clean-up on Xn-U Address Indication procedure	R3 (Intel Corporation, ZTE)
R2-2108871	Clean-up on Xn-U Address Indication procedure	R3 (Intel Corporation, ZTE)
R2-2108872	NAS PDU handling	R3 (Ericsson, CATT, Huawei, ZTE, Nokia, Nokia Shanghai Bell)
R2-2108988	Reserved for breakout session	MCC
R2-2108989	Reserved for breakout session	MCC
R2-2108996	Reserved for breakout session	MCC
R2-2108998	Reserved for breakout session	MCC
R2-2109007	NAS PDU handling	R3 (Ericsson, CATT, Huawei, ZTE, Nokia, Nokia Shanghai Bell)
R2-2109009	Reserved for breakout session	MCC
R2-2109010	Reserved for breakout session	MCC
R2-2109011	Reserved for breakout session	MCC
R2-2109012	Reserved for breakout session	MCC
R2-2109013	Reserved for breakout session	MCC
R2-2109014	Reserved for breakout session	MCC
R2-2109015	Reserved for breakout session	MCC
R2-2109187	Ununsed	RAN2
R2-2109220	Reserved for breakout session	MCC
3	Incoming liaisons
R2-2106975	Reply LS on User location identification from Carrier Aggregation secondary cell activation messages (S3-212305; contact: Huawei)	SA3
R2-2106984	LS on Bearer pre-emption rate limit issue for GBR bearer establishment in MC systems (S6-211829; contact: Motorola Solutions)	SA6
R2-2108167	Discussion on SA6 LS on Bearer pre-emption rate limit issue for GBR bearer establishment in MC systems	Ericsson
4.2	eMTC corrections Rel-15 and earlier
R2-2107773	Key stream reuse issue of EDT and PUR	NEC
4.4	Positioning corrections Rel-15 and earlier
R2-2107260	Further discussion on Positioning SI message scheduling for eMTC	Lenovo, Motorola Mobility
R2-2107261	Addition of scheduling restrictions of positioning SI messages for eMTC	Lenovo, Motorola Mobility
R2-2107262	Addition of scheduling restrictions of positioning SI messages for eMTC	Lenovo, Motorola Mobility
R2-2107784	Correction on ProvideCapabilities and ProvideLocationInformation	Samsung
R2-2108931	Report from email discussion [AT115-e][601][POS] AI 4.4 Positioning corrections Rel-15 and earlier (Lenovo)	Lenovo
4.5	Other LTE corrections Rel-15 and earlier
R2-2108312	On T330 resetting	Ericsson, ZTE Corporation, Sanechips
R2-2108634	Minor changes collected by Rapporteur for Rel-15	Samsung
R2-2108635	Minor changes collected by Rapporteur for Rel-16	Samsung (rapporteur)
R2-2108851	[AT115-e][201][LTE] Miscellaneous LTE CRs	Samsung
R2-2108852	On T330 resetting	Ericsson, ZTE Corporation, Sanechips
R2-2108866	Minor changes collected by Rapporteur	Samsung (rapporteur)
R2-2108867	Minor changes collected by Rapporteur	Samsung (rapporteur)
5.2.2	TS 37.340
R2-2108183	Clarification on RACH procedure for HO with PSCell	Ericsson
R2-2108184	Clarification on RACH procedure for HO with PSCell	Ericsson
R2-2108211	Clarification on RACH procedure for HO with PSCell	Ericsson
R2-2108212	Clarification on RACH procedure for HO with PSCell	Ericsson
5.3	User Plane corrections
R2-2109097	Report of [AT115-e][011][NR15] User plane corrections	Huawei, HiSilicon
R2-2109098	LS on initial state of elements controlled by MAC Ces	RAN2
5.3.1	MAC
R2-2107224	Clarification on UE behaviors for de-/activation MAC CEs	Qualcomm Incorporated
R2-2107616	Discussion on GSMA LS on SPARROW attack	Apple
R2-2108264	Correction on the term of the handover in handling of MAC CE	ZTE Corporation, Nokia, Nokia Shanghai Bell
R2-2108265	Correction on the term of the handover in handling of MAC CE	ZTE Corporation, Nokia, Nokia Shanghai Bell
R2-2108597	Discussion on MAC behavior for suspended radio bearers	Huawei, HiSilicon
R2-2108598	Correction on MAC behavior for suspended radio bearers for Rel-15	Huawei, HiSilicon
R2-2108599	Correction on MAC behavior for suspended radio bearers for Rel-16	Huawei, HiSilicon
R2-2108600	Clarification on the activation status for semi-persistent resource and indications	Huawei, HiSilicon
R2-2108601	Clarification on the activation status for semi-persistent resource and indications	Huawei, HiSilicon
R2-2108782	Handling of suspended RB	LG Electronics UK
R2-2108819	On BSR calculation for suspended raio bearers	MediaTek Inc.
5.3.2	RLC PDCP SDAP
R2-2107666	RLC Clean-up CR	Samsung
R2-2107667	RLC Clean-up CR	Samsung
R2-2108844	RLC Clean-up CR	Samsung, MediaTek
R2-2108845	RLC Clean-up CR	Samsung, MediaTek
5.4.1.1	Connection control
R2-2107373	38331 Clarifications on securityConfig in RadioBearerConfig-R15	OPPO
R2-2107374	38331 Clarifications on securityConfig in RadioBearerConfig-R16	OPPO
R2-2107375	38331 Clarifications on full configuration-R15	OPPO
R2-2107376	38331 Clarifications on full configuration-R16	OPPO
R2-2107418	38331 Clarifications on RadioBearerConfig-R15	OPPO
R2-2107419	38331 Clarifications on RadioBearerConfig-R16	OPPO
R2-2107570	Clarification on LTE HO without SCG Configuration Change	Apple
R2-2107617	Discussion on RRC handling of NAS triggers not subject to UAC	Apple
R2-2107618	T302 check when NAS triggers RRC connection resume	Apple
R2-2107619	T302 check when NAS triggers RRC connection resume	Apple
R2-2107770	Discussion on timer expiry after RRCRelease reception	NEC
R2-2107771	Clarification on timer expiry after RRCRelease reception	NEC
R2-2107772	Clarification on timer expiry after RRCRelease reception	NEC
R2-2107836	Correction on the Need for SCG Reconfiguration with Sync in (NG)EN-DC	vivo
R2-2107837	Correction on the Need for SCG Reconfiguration with Sync in (NG)EN-DC	vivo
R2-2107838	Correction on the Release Cause for RRC_INACTVE UE	vivo
R2-2107839	Correction on the Release Cause for RRC_INACTVE UE	vivo
R2-2108185	Clarification on NR SCG reconfiguration with sync in LTE	Ericsson
R2-2108186	Clarification on NR SCG reconfiguration with sync in LTE	Ericsson
R2-2108187	Release of RadioBearerConfig during MR-DC release	Ericsson
R2-2108188	Release of RadioBearerConfig during MR-DC release	Ericsson
R2-2108368	Discussion on BWP switch for TDD	ZTE Corporation, Sanechips
R2-2108369	Correction on firstActiveBWP-Id for TDD	ZTE Corporation, Sanechips
R2-2108370	Correction on firstActiveBWP-Id for TDD(R16)	ZTE Corporation, Sanechips
R2-2108371	Correction on rach-ConfigBFR	ZTE Corporation, Sanechips
R2-2108372	Correction on rach-ConfigBFR(R16)	ZTE Corporation, Sanechips
R2-2108373	Correction on plmn-IdentityList	ZTE Corporation, Sanechips
R2-2108374	Correction on plmn-IdentityList(R16)	ZTE Corporation, Sanechips
R2-2108415	E-mail discussion summary of [Post114-e][070][NR15] Common Fields in Dedicated Signalling	Ericsson (Rapporteur)
R2-2108616	Adding RRC processing delay for HO from E-UTRA to NR	Huawei, HiSilicon
R2-2108617	Adding RRC processing delay for HO from E-UTRA to NR	Huawei, HiSilicon
R2-2108636	Corrections on the absent condition of csi-ReportingBand	Samsung
R2-2108637	Corrections on the absent condition of csi-ReportingBand	Samsung
R2-2108811	Correction on reconfigurationWithSync	Huawei, HiSilicon
R2-2108812	Correction on reconfigurationWithSync	Huawei, HiSilicon
R2-2109067	Report of [AT115-e][012][NR15] Connection Control I (OPPO)	OPPO
R2-2109075	Summary of [AT115-e][039][NR15] Connection Control III (Apple)	Apple
R2-2109081	Correction on firstActiveBWP-Id for TDD	ZTE Corporation, Sanechips
R2-2109082	Correction on firstActiveBWP-Id for TDD(R16)	ZTE Corporation, Sanechips
R2-2109086	Clarification on RRC processing delay for HO from E-UTRA to NR	Huawei, HiSilicon
R2-2109087	Clarification on RRC processing delay for HO from E-UTRA to NR	Huawei, HiSilicon
R2-2109153	[Draft] LS on NAS procedure not subject to UAC	Apple
R2-2109179	Summary of [AT115-e][013][NR15] Connection Control II (vivo)	vivo
R2-2109180	Correction on the Release Cause for RRC_INACTVE UE	vivo
R2-2109181	Correction on the Release Cause for RRC_INACTVE UE	vivo
R2-2109205	LS on NAS procedure not subject to UAC	RAN2
R2-2109211	Correction on reconfigurationWithSync	Huawei, HiSilicon, Apple
R2-2109212	Correction on reconfigurationWithSync	Huawei, HiSilicon, Apple
R2-2109232	Correction on reconfigurationWithSync	Huawei, HiSilicon, Apple
R2-2109233	Correction on reconfigurationWithSync	Huawei, HiSilicon, Apple
5.4.1.3	Other
R2-2107022	Discussion on RMSI and OSI reception based on non-zero search space	OPPO
R2-2107377	38331 Corrections on MeasObjectEUTRA-R15	OPPO
R2-2107378	38331Corrections on MeasObjectEUTRA-R16	OPPO
R2-2107573	Clarification on L3 filtering configuration (filterCoefficient)	Apple
R2-2108290	Miscellaneous non-controversial corrections Set XI	Ericsson
R2-2108571	Clarification for overheating assistance information reporting	Huawei, HiSilicon
R2-2108644	Clarification of search space configuration for SIB1	Huawei, HiSilicon
R2-2108645	Clarification of search space configuration for SIB1	Huawei, HiSilicon
R2-2108646	Correction on inter-RAT measurement report triggering	Huawei, HiSilicon
R2-2108647	Correction on inter-RAT measurement report triggering	Huawei, HiSilicon
R2-2109157	LS on RMSI reception based on non-zero search space	RAN2
R2-2109209	Summary of [AT115-e][014][NR15] CP Other – Phase 1	Huawei, HiSilicon
R2-2109210	Summary of [AT115-e][014][NR15] CP Other – Phase 2	Huawei, HiSilicon
R2-2109221	LS on RMSI reception based on non-zero search space	RAN2
R2-2109228	Miscellaneous non-controversial corrections Set XI	Ericsson
R2-2109230	Miscellaneous non-controversial corrections Set XI	Ericsson
5.4.3	UE capabilities
R2-2106908	Reply LS on RI bit width for Cat5 UE in EN-DC mode (R1-2106108; contact: Nokia)	RAN1
R2-2106909	Reply LS on fallback applicability for FeatureSetDownLinkPerCC capability fields (R1-2106133; contact: ZTE)	RAN1
R2-2106956	Reply LS on the Intra-band and Inter-band (NG)EN-DC/NE-DC Capabilities (R4-2107907; contact: ZTE)	RAN4
R2-2106958	Reply LS on simultaneous Rx/Tx capability (R4-2108003; contact: Qualcomm)	RAN4
R2-2106963	Reply LS on simultaneous Rx/Tx capability (R4-2111452; contact: Huawei)	RAN4
R2-2107130	Simultaneous Rx/Tx UE capability	Qualcomm Incorporated
R2-2107389	Considerations on simultaneous Rx/Tx capability per band pair	NTT DOCOMO, Inc.
R2-2107390	UE Capability filtering solution for EN-DC BC selection issue	NTT DOCOMO, Inc.
R2-2107600	Correction to the description of additionalActiveTCI-StatePDCCH	Apple
R2-2107601	Correction to the description of additionalActiveTCI-StatePDCCH	Apple
R2-2107977	Definition of fallback per CC feature set	Ericsson, ZTE Corporation, Sanechips
R2-2107978	Definition of fallback per CC feature set	Ericsson, ZTE Corporation, Sanechips
R2-2107980	Allowed bandwidth in BWP configuration	Ericsson
R2-2108038	CR on the Intra-band and Inter-band EN-DC Capabilities - R15	ZTE Corporation, Sanechips
R2-2108039	CR on the Intra-band and Inter-band EN-DC Capabilities - R16	ZTE Corporation, Sanechips
R2-2108346	Clarification to RI bit width for Cat5 in EN-DC	Nokia, Nokia Shanghai Bell
R2-2108379	Resolving unclarity in fallback band combination definition	Ericsson
R2-2108380	Resolving unclarity in fallback band combination definition	Ericsson
R2-2108381	Resolving unclarity in fallback band combination definition	Ericsson
R2-2108382	Resolving unclarity in fallback band combination definition	Ericsson
R2-2108572	Clarification on the simultaneousRxTxInterBandCA capability in NR-DC	Huawei, HiSilicon, Ericsson
R2-2108573	Clarification on the simultaneousRxTxInterBandCA capability in NR-DC	Huawei, HiSilicon, Ericsson
R2-2108574	Introduction of NR channel bandwidth capability for LTE-to-NR HO case	Huawei, HiSilicon
R2-2108575	Introduction of NR channel bandwidth capability for LTE-to-NR HO case	Huawei, HiSilicon
R2-2108576	Clarifcation on BC fallback and spCellPlacement	Huawei, HiSilicon
R2-2108577	Clarifcation on BC fallback and spCellPlacement	Huawei, HiSilicon
R2-2108578	Support of newly introuduced 100M bandwidth for band n40	Huawei, HiSilicon
R2-2108579	CR for the support of newly introuduced 100M bandwidth for band n40	Huawei, HiSilicon
R2-2108580	CR for the support of newly introuduced 100M bandwidth for band n40	Huawei, HiSilicon
R2-2108581	Correction on fallback band combination for SUL	Huawei, HiSilicon
R2-2108582	Correction on fallback band combination for SUL	Huawei, HiSilicon
R2-2108583	Correction on fallback band combination for SUL	Huawei, HiSilicon
R2-2108584	Correction on fallback band combination for SUL	Huawei, HiSilicon
R2-2108718	Clarification on IMS video over split bearer in (NG)EN-DC	Google Inc.
R2-2108719	Clarification on IMS video over split bearer in (NG)EN-DC	Google Inc.
R2-2108749	Clarification on IMS video over split bearer in NR-DC and NE-DC	Google Inc.
R2-2108751	Clarification on IMS video over split bearer in NR-DC and NE-DC	Google Inc.
R2-2109048	Correction to the description of additionalActiveTCI-StatePDCCH	Apple Inc
R2-2109049	Correction to the description of additionalActiveTCI-StatePDCCH	Apple Inc
R2-2109062	Summary of offline [AT115-e][017][NR15] UE Capabilties III (ZTE)	ZTE, Sanechips
R2-2109063	CR on the Intra-band and Inter-band EN-DC Capabilities - R15	ZTE Corporation, Sanechips
R2-2109064	CR on the Intra-band and Inter-band EN-DC Capabilities - R16	ZTE Corporation, Sanechips
R2-2109092	Clarification to RI bit width for Cat5 UEs in EN-DC	Nokia
R2-2109138	Summary of offline 015 Rel-15 UE caps I	Ericsson
R2-2109139	Definition of fallback per CC feature set	Ericsson, ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell
R2-2109140	Definition of fallback per CC feature set	Ericsson, ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell
R2-2109161	Clarification to RI bit width for Cat5 UEs	Nokia, Nokia Shanghai Bell
R2-2109162	Summary of [AT115-e][016][NR15] UE Capabilities II	Huawei, HiSilicon
R2-2109164	Support of newly introduced 100M bandwidth for band n40	Huawei, HiSilicon
R2-2109165	Support of newly introduced 100M bandwidth for band n40	Huawei, HiSilicon
R2-2109166	Clarification on the simultaneousRxTxInterBandCA capability in NR-DC	Huawei, HiSilicon, Ericsson
R2-2109167	Clarification on the simultaneousRxTxInterBandCA capability in NR-DC	Huawei, HiSilicon, Ericsson
R2-2109188	Simultaneous Rx/Tx UE capability per band pair	NTT DOCOMO, INC.
R2-2109189	Simultaneous Rx/Tx UE capability per band pair	NTT DOCOMO, INC.
R2-2109190	Simultaneous Rx/Tx UE capability per band pair	NTT DOCOMO, INC.
R2-2109191	Simultaneous Rx/Tx UE capability per band pair	NTT DOCOMO, INC.
5.4.4	Idle/inactive mode procedures
R2-2107263	Corrections to intra-frequency cell reselection for MIB, SIB1 acquisition failure and TAC absence in SIB1	Lenovo, Motorola Mobility
R2-2108364	Clarification of barring when TAC is missing in RAN sharing	Qualcomm Incorporated
R2-2108365	Clarification of barring when TAC is missing in RAN sharing	Qualcomm Incorporated
R2-2108481	Cell barring due to SIB1 acquisition failure	Lenovo, Motorola Mobility
R2-2108912	Correction to cell selection and reselection due to SIB1 acquisition failure	Lenovo, Motorola Mobility
R2-2108913	Correction to cell selection and reselection due to SIB1 acquisition failure	Lenovo, Motorola Mobility
R2-2109110	Clarification of barring when TAC is missing in RAN sharing	Qualcomm Incorporated, Ericsson
R2-2109111	Clarification of barring when TAC is missing in RAN sharing	Qualcomm Incorporated, Ericsson
5.5	Positioning corrections
R2-2106928	Reply LS on E-CID LTE measurement in Rel-15 measurements (R3-212802; contact: Huawei)	RAN3
R2-2107329	Correction to E-CID-R15	Huawei, HiSilicon
R2-2107330	Correction to E-CID-R16	Huawei, HiSilicon
R2-2107785	Correction on ProvideCapabilities and ProvideLocationInformation	Samsung
R2-2107786	Correction on ProvideCapabilities and ProvideLocationInformation	Samsung
R2-2108407	Correction for Roles of gNB and ng-eNB for positioning in release-15	Ericsson
R2-2108876	Correction for Role of gNB for positioning in release-15	Ericsson
R2-2108932	[AT115-e][Offline-602][POS] AI 5.5 Positioning corrections (Huawei)	Huawei, HiSilicon
R2-2108952	Correction to UL E-CID	Huawei, HiSilicon, Ericsson
R2-2108953	Correction to UL E-CID-R16	Huawei, HiSilicon
R2-2108954	Correction for Roles of gNB and ng-eNB for positioning in release-15	Ericsson
6.1.1	Organisational
R2-2106937	Response LS on Exchange of information related to SRS-RSRP measurement resource configuration for UE-CLI (R3-212889; contact: ZTE)	RAN3
R2-2106943	Reply LS on LS Reply on QoS Monitoring for URLLC (R3-212937; contact: Huawei)	RAN3
R2-2106959	LS on RRM relaxation in power saving (R4-2108230; contact: CATT, Ericsson)	RAN4
6.1.2	Stage 2 corrections
R2-2109099	Report of [AT115-e][018][NR15NR16] Stage-2 (Huawei)	Huawei, HiSilicon
6.1.2.1	TS 3x.300
R2-2106914	LS on correction to Rel-16 HARQ description in TS38.300 (R1-2106205; contact: Huawei)	RAN1
R2-2107165	Correction to Rel-16 HARQ description	Huawei, HiSilicon
R2-2107664	CR for duplication deactivation	Samsung
R2-2108344	Clarification of PNI-NPN and NE-DC	Qualcomm Incorporated
R2-2108602	Miscellaneous corrections to eURLLC for 38.300	Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, OPPO
R2-2109069	Correction to Rel-16 HARQ description	Huawei, HiSilicon
R2-2109100	Miscellaneous corrections to eURLLC for 38.300	Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, OPPO, CATT
6.1.2.2	TS 37.340
R2-2108439	Corrections for fast MCG link recovery	Huawei, HiSilicon
6.1.3	User Plane corrections
R2-2109084	Report of [AT114-e][019][NR16] MAC I	vivo
R2-2109085	LS to RAN1 on UL skipping with LCH-based prioritization	RAN2
R2-2109192	Summary for the offline [AT115-e][021][NR16] MAC III (ZTE)	ZTE Corporation (rapporteur)
6.1.3.1	MAC
R2-2106926	LS on UL skipping for PUSCH in Rel-16 (R1-2106370; contact: vivo)	RAN1
R2-2106997	Correction on UL Skipping for PUSCH in Rel-16	vivo, ZTE corporation, Xiaomi Communications
R2-2107010	Corrections to SCell BFR	Samsung Electronics Co., Ltd
R2-2107062	Discussion on reporting multiplexed CSI on PUCCH	OPPO
R2-2107160	Discussion about a loophole for R16 uplink skipping procedure	Huawei, HiSilicon
R2-2107161	Correction on R16 uplink skipping procedure	Huawei, HiSilicon
R2-2107162	Discussion on the condition of lch-basedPrioritization for UL skipping	Huawei, HiSilicon
R2-2107163	Discussion on R16 uplink skipping with TB repetitions	Huawei, HiSilicon
R2-2107164	Discussion on reporting multiplexed CSI on PUCCH	Huawei, HiSilicon
R2-2107197	Overlapping UCI and PUSCH	CATT
R2-2107198	Correction on UL skipping with lch-basedPrioritization	CATT, Samsung
R2-2107199	Handling of Multi-TB CGs in MAC	CATT
R2-2107200	Handling of pending empty PDUs after UCI multiplexing	CATT
R2-2107481	Correction on starting of RetransmissionTimerDL	ZTE Corporation, Sanechips
R2-2107569	Clarification on ConfigurationGrantTimer operation with the repetition transmission	Apple
R2-2107609	Enhanced UL skipping with intra-UE prioritization	Apple
R2-2107610	UCI multiplexing and overlapped SR/PUSCH	Apple
R2-2107656	Clarification on reporting multiplexed CSI on PUCCH	OPPO, Nokia, ZTE
R2-2107735	Ignoring the retransmission grant overlapped with UCI	OPPO
R2-2107782	Clarification on E-UTRA MAC entity in PHR	Samsung
R2-2107927	CR on the enabling restriction on R16 PUSCH skipping and PUSCH repetitions	OPPO
R2-2108092	Corrections to R16 UL skipping with repetitions	Ericsson, NTT DOCOMO INC.
R2-2108093	Corrections to R16 UL skipping with repetitions	Ericsson, NTT DOCOMO INC.
R2-2108094	Corrections to retransmission of configured grant with empty buffer	Ericsson, MediaTek Inc.
R2-2108095	Corrections to retransmission of configured grant with empty buffer	Ericsson, MediaTek Inc.
R2-2108096	Corrections to pdsch-HARQ-ACK-CodeBookList	Ericsson
R2-2108120	Condition for setting LBT_COUNTER to Zero	ZTE Wistron Telecom AB
R2-2108232	On enhanced UL skipping and PUSCH repetitions	MediaTek Inc.
R2-2108257	Clarification of PUCCH resource in LCH-based Prioritization	Samsung
R2-2108266	Correction to 38.321 on application of the information element for extension	ZTE Corporation, Samsung
R2-2108267	Correction to 38.321 on priority handling about the UL grant addressed to TC-RNTI	ZTE Corporation, Sanechips
R2-2108283	Autonomous Transmission of MAC PDU with only Padding or Periodic BSR	Nokia, Nokia Shanghai Bell
R2-2108284	Avoiding autonomous transmission of MAC PDU with only Padding BSR or unuseful Periodic BSR – Option 1	Nokia, Nokia Shanghai Bell
R2-2108285	Avoiding autonomous transmission of MAC PDU with only Padding BSR or unuseful Periodic BSR – Option 2	Nokia, Nokia Shanghai Bell
R2-2108343	Start of DRX RTT timer for one-shot HARQ feedback	Qualcomm Incorporated
R2-2108603	Correction to MsgA grant overlapping with another UL grant for a HARQ process	Huawei, HiSilicon
R2-2108767	38.321_CRxxxx_(Rel-16)_R2-210xxxx Periodic CSI report with DCP	LG Electronics UK
R2-2108781	Stopping configuredGrantTimer upon ignored or skipped uplink grant	LG Electronics UK
R2-2108785	Periodic CSI reporting with DCP	LG Electronics UK
R2-2108787	UCI on retransmission uplink grant	LG Electronics UK
R2-2109045	Corrections to pdsch-HARQ-ACK-CodeBookList	Ericsson
R2-2109057	Report of Offline 020: MAC II	Samsung
R2-2109068	Correction on R16 uplink skipping procedure	Huawei, HiSilicon, vivo, Samsung
R2-2109115	Start of DRX RTT timer for one-shot HARQ feedback	Qualcomm Incorporated
R2-2109156	Clarification of PUCCH resource in LCH-based Prioritization	Samsung, CATT, Apple
R2-2109158	Clarification on E-UTRA MAC entity in PHR	Samsung
R2-2109193	Correction to 38.321 on priority handling of the UL grant addressed to TC-RNTI	ZTE Corporation, Sanechips
R2-2109214	Correction on UL Skipping for PUSCH in Rel-16	vivo, ZTE corporation, Xiaomi Communications, MediaTek Inc., OPPO
6.1.3.2	RLC
R2-2108247	Retransmission conditions upon expiry of t-PollRetransmit	Nokia, Nokia Shanghai Bell
R2-2108248	Conditions for incrementing RETX_COUNT	Nokia, Nokia Shanghai Bell
R2-2108249	Retransmission conditions upon expiry of t-PollRetransmit	Nokia, Nokia Shanghai Bell
R2-2109149	Report of [AT115-e][022][NR16] RLC & PDCP (Nokia)	Nokia, Nokia Shanghai Bell
6.1.3.3	PDCP
R2-2107662	CR for LTE PDCP operation after DAPS release	Samsung
R2-2107665	CR for the ciphering of EHC header	Samsung
R2-2109076	CR for LTE PDCP operation after DAPS release	Samsung, Ericsson
R2-2109160	CR for the ciphering of EHC header	Samsung, LG Electronics
6.1.4.1.1	Connection control
R2-2106916	Reply LS on random value generation for RMTC-SubframeOffset (R1-2106264; contact: Apple)	RAN1
R2-2106933	Response LS on Conditional Handover with SCG configuration scenarios (R3-212848; contact: Nokia)	RAN3
R2-2106955	Reply LS DC location reporting for intra-band UL CA (R4-2107903; contact: Huawei)	RAN4
R2-2107085	Discussion on T301 issue for DAPS HO	OPPO
R2-2107086	Correction on T301 for DAPS HO (alternative 1)	OPPO
R2-2107087	Correction on T301 for DAPS HO (alternative 2)	OPPO
R2-2107401	Correction on TCI configuration for DCI format 1_2	vivo
R2-2107526	On supporting CHO with SCG configuration	Nokia, Nokia Shanghai Bell
R2-2107527	Response LS on CHO with SCG configuration	Nokia, Nokia Shanghai Bell
R2-2107571	RRC Processing Delay for SCell Modification	Apple
R2-2107588	RSSI/CO reporting in MCG/SCGfailureinformation	Apple
R2-2107599	Correction to uplink Tx DC location reporting for UL CA 2PA case	Apple
R2-2107775	Correction on fallback to source SDAP configuration in case of DAPS failure	NEC
R2-2107776	Correction on SRB handling for DAPS	NEC
R2-2108090	On bearer release handling for DAPS HO	Nokia, Nokia Shanghai Bell
R2-2108102	RRC connection re-establishment with CPC configuration	Ericsson
R2-2108103	RRC connection re-establishment with CPC configuration	Ericsson
R2-2108106	Clarification on RMTC subframe offset	Ericsson
R2-2108164	Discussion on CHO with SCG configuration	ZTE Corporation, Sanechips
R2-2108440	Corrections on RRC reconfiguration for fast MCG link recovery	Huawei, HiSilicon
R2-2108441	Corrections on RRC reconfiguration for fast MCG link recovery	Huawei, HiSilicon
R2-2108473	Correction on RepetitionSchemeConfig for eMIMO	Huawei, HiSilicon
R2-2108638	UE reporting of Tx DC location info for the second PA	Huawei, HiSilicon
R2-2108817	Correction to DAPS handover	Google Inc.
R2-2109053	Report from [AT115-e][024][NR16] DAPS & CHO (Nokia)	Nokia, Nokia Shanghai Bell
R2-2109066	Corrections on RRC reconfiguration for fast MCG link recovery	Huawei, HiSilicon
R2-2109080	Corrections on RRC reconfiguration for fast MCG link recovery	Huawei, HiSilicon
R2-2109090	CR for UE reporting Tx DC location info for the second PA	Huawei, HiSilicon
R2-2109144	Correction to DAPS handover	Google Inc.
R2-2109154	Summary of [AT115-e][023][NR16] Connection Control I (Apple)	Apple Inc
R2-2109155	Correction on TCI configuration for DCI format 1_2	vivo, Nokia, Nokia Shanghai Bell
R2-2109170	No support for CHO with SCG configuration	Nokia, Nokia Shanghai Bell, ZTE Corporation, Sanechips
R2-2109171	No support for CHO with SCG configuration	Nokia, Nokia Shanghai Bell, ZTE Corporation, Sanechips
R2-2109172	Response LS on CHO with SCG configuration	RAN2
6.1.4.1.2	RRM and Measurements
R2-2107462	Impact of SNPN Access Mode to Idle/inactive measurement	FGI, Asia Pacific Telecom
R2-2107504	Corrections of Idle/inactive measurement under SNPN Access Mode	FGI, Asia Pacific Telecom
R2-2108104	Modification of measId for conditional reconfiguration	Ericsson
R2-2108105	Modification of measId for conditional reconfiguration	Ericsson
R2-2108288	Measurement and gap configuration for Need for Gaps	Ericsson
R2-2108289	Clarification on measurement and measurement gap configuration	Ericsson
R2-2108652	NeedForGap Clarification	Qualcomm Incorporated
R2-2109046	NeedForGap Clarification	Qualcomm Incorporated
R2-2109055	Report of [AT115-e][025][NR16] RRM & Measurements (Ericsson)	Ericsson
R2-2109150	Modification of measId for conditional reconfiguration	Ericsson
R2-2109151	Modification of measId for conditional reconfiguration	Ericsson
6.1.4.1.3	System Information and Paging
R2-2107011	Corrections to SIB validity for NPN only cell	Samsung Electronics Co., Ltd
R2-2107722	PO determination in RRC_INACTIVE for Rel-16 and later releases	ZTE corporation, Ericsson,CMCC, China Telecom, China Unicom,vivo, Sanechips
R2-2107723	Correction on PO determination for UE in inactive state-38.331	ZTE corporation, Ericsson,CMCC, China Telecom, China Unicom,vivo, Sanechips
R2-2107724	Correction on PO determination for UE in inactive state-38.304	ZTE corporation, Ericsson,CMCC, China Telecom, China Unicom,vivo, Sanechips
R2-2107725	Correction on PO determination for UE in inactive state-38.306	ZTE corporation, Ericsson,CMCC, China Telecom, China Unicom,vivo, Sanechips
R2-2107726	Correction on PO determination for UE in inactive state-36.331	ZTE corporation, Ericsson,CMCC, China Telecom, China Unicom,vivo, Sanechips
R2-2107727	Correction on PO determination for UE in inactive state-36.304	ZTE corporation, Ericsson,CMCC, China Telecom, China Unicom,vivo, Sanechips
R2-2107728	Correction on PO determination for UE in inactive state-36.306	ZTE corporation, Ericsson,CMCC, China Telecom, China Unicom,vivo, Sanechips
R2-2107934	Clarification on the NPN-IdentityInfoList	Samsung
R2-2108107	MIB correction on subCarrierSpacingCommon	Ericsson
R2-2108615	Clarification on encoding format for HRNN	Huawei, HiSilicon
R2-2108879	CR to 36.331 on correcting Rel-15 failure type definition	Huawei, HiSilicon
R2-2108880	CR to 38.331 on correcting Rel-15 failure type definition	Huawei, HiSilicon
R2-2108918	CR to 36.331 on correcting Rel-15 failure type definition	Huawei, HiSilicon
R2-2108919	CR to 38.331 on correcting Rel-15 failure type definition	Huawei, HiSilicon
R2-2109006	Clarification on the NPN-IdentityInfoList	Samsung
R2-2109074	Corrections to SIB validity for NPN only cell	Samsung Electronics
R2-2109077	Report of [AT115-e] [026] [NR16] System Information and Paging (ZTE) – First round	ZTE corporation, Sanechips
R2-2109116	Clarification on encoding format for HRNN	Huawei, HiSilicon
R2-2109169	MIB correction on subCarrierSpacingCommon	Ericsson
R2-2109174	CR to 36.331 on correcting Rel-15 failure type definition	Huawei, HiSilicon
R2-2109175	CR to 38.331 on correcting Rel-15 failure type definition	Huawei, HiSilicon
6.1.4.1.4	Inter-Node RRC messages
R2-2108776	Signalling of HOReqACK msg upon serving cell configuration update	Samsung Electronics
R2-2108777	[Draft] LS on reflecting source cell configuration update in Conditional Handover	Samsung Electronics
6.1.4.1.5	Other
R2-2106911	LS on the description of RRC parameter p0-AlphaSets (R1-2106168; contact: ZTE)	RAN1
R2-2106996	Correction on msg1-SubcarrierSpacing and msgA-SubcarrierSpacing	vivo
R2-2107129	Early implementation of eCall over IMS in NR	Qualcomm Incorporated, Ericsson, Vodafone
R2-2107285	Report of email discussion [Post114-e][071][NR16] CandidateBeamRSList set to release (MediaTek)	MediaTek Inc.
R2-2107286	Handling of candidateBeamRSListExt-v1610 (option A1)	MediaTek Inc.
R2-2107287	Handling of candidateBeamRSListExt-v1610 (option B)	MediaTek Inc.
R2-2107288	Handling of candidateBeamRSListExt-v1610 (option C)	MediaTek Inc.
R2-2107482	Correction on description of lbt-FailureInstanceMaxCount in LBT-FailureRecoveryConfig	ZTE Corporation, Sanechips
R2-2107485	Correction to description of po-AlfphaSets	ZTE Corporation, Sanechips
R2-2108268	Correction to 38.331 on the field description of msgA-TransMax	ZTE Corporation, vivo, LG Electronics, OPPO, Samsung
R2-2108291	Miscellaneous non-controversial corrections Set XI	Ericsson
R2-2108434	Correction on Redirection with MPS Indication	Peraton Labs, CISA ECD, T-Mobile US, Ericsson , Qualcomm, NTT DoCoMo, AT&T, Verizon
R2-2108587	Correction on RRC multiplicity and type constraint definitions	Huawei, HiSilicon
R2-2108878	Email report of [Post115-e][063][NR16] SCG failure information (Huawei)	Huawei
R2-2108910	LS on the security issue of MBS interest indication	RAN2
R2-2109071	Correction to description of p0-AlphaSets	ZTE Corporation, Sanechips
R2-2109095	[AT115-e][027][NR16] CP Other & LTE – Intermediate report	Ericsson
R2-2109096	[AT115-e][027][NR16] CP Other & LTE – Final report	Ericsson
R2-2109202	Handling of candidateBeamRSListExt-v1610 (option A1)	MediaTek Inc.
R2-2109229	Miscellaneous non-controversial corrections Set XI	Ericsson
R2-2109231	Miscellaneous non-controversial corrections Set XI	Ericsson
6.1.4.2	LTE changes
R2-2108189	ASN.1 misalignment for the SCGFailureInformationNR message	Ericsson
R2-2108190	ASN.1 misalignment for the SCGFailureInformationNR message	Ericsson
R2-2108375	Correction on ULInformationTransferMRDC(R16)	ZTE Corporation, Sanechips
R2-2108569	Discussion on compatibility issue and solutions for Rel-15 failure type definition	Huawei, HiSilicon
R2-2108679	Discussion on compatibility issue on failure type for NR SCG failure	CATT
R2-2109083	Correction on ULInformationTransferMRDC	ZTE Corporation, Sanechips
6.1.4.3	UE capabilities
R2-2106925	LS on updated Rel-16 RAN1 UE features lists for NR after RAN1#105-e (R1-2106345; contact: NTT DOCOMO, AT&T)	RAN1
R2-2106952	LS on UL MIMO coherence for Tx switching between two carriers (R4-2107765; contact: China Telecom)	RAN4
R2-2106960	LS on Rel-16 updated RAN4 UE features lists for LTE and NR (R4-2108333; contact: CMCC)	RAN4
R2-2107342	Correction on the capability field DiffSCS-DAPS	Huawei, HiSilicon
R2-2107935	Inter-operability of band n77 extension in US	Nokia, Nokia Shanghai Bell
R2-2107936	Distinguishing support of extended band n77 for EN-DC, Alt.1 (R16, 36306)	Nokia, Nokia Shanghai Bell
R2-2107937	Distinguishing support of extended band n77 for EN-DC, Alt.1 (R16, 36331)	Nokia, Nokia Shanghai Bell
R2-2107938	Distinguishing support of extended band n77 for NR, Alt.1 (R16, 38306)	Nokia, Nokia Shanghai Bell
R2-2107939	Distinguishing support of extended band n77 for NR, Alt.1 (R16, 38331)	Nokia, Nokia Shanghai Bell
R2-2107940	Distinguishing support of extended band n77 for EN-DC, Alt.2 (R15, 36306)	Nokia, Nokia Shanghai Bell
R2-2107941	Distinguishing support of extended band n77 for EN-DC, Alt.2 (R16, 36306)	Nokia, Nokia Shanghai Bell
R2-2107942	Distinguishing support of extended band n77 for EN-DC, Alt.2 (R15, 36331)	Nokia, Nokia Shanghai Bell
R2-2107943	Distinguishing support of extended band n77 for EN-DC, Alt.2 (R16, 36331)	Nokia, Nokia Shanghai Bell
R2-2107944	Distinguishing support of extended band n77 for NR, Alt.2 (R15, 38306)	Nokia, Nokia Shanghai Bell
R2-2107945	Distinguishing support of extended band n77 for NR, Alt.2 (R16, 38306)	Nokia, Nokia Shanghai Bell
R2-2107946	Distinguishing support of extended band n77 for NR, Alt.2 (R15, 38331)	Nokia, Nokia Shanghai Bell
R2-2107947	Distinguishing support of extended band n77 for NR, Alt.2 (R16, 38331)	Nokia, Nokia Shanghai Bell
R2-2108287	Band n77 issues in the US	Ericsson
R2-2108332	UE capability signalling for Band n77 Ues	DENSO CORPORATION
R2-2108468	Correction to ul-FullPwrMode capability	Sequans Communications
R2-2108480	Miscellaneous corrections to UE capability descriptions	Lenovo, Motorola Mobility
R2-2108585	Correction on PDCCH Blind Detection in CA	Huawei, HiSilicon
R2-2108586	Correction on PDCCH Blind Detection in CA	Huawei, HiSilicon
R2-2108618	Adding UE capability of UL MIMO coherence for UL Tx switching	Huawei, HiSilicon, China Telecom, Apple
R2-2108619	Adding UE capability of UL MIMO coherence for UL Tx switching	Huawei, HiSilicon, China Telecom, Apple
R2-2108641	Correction on the capability field DiffSCS-DAPS	Huawei, HiSilicon
R2-2108651	FR1FR2 differentiation for enhanced UL grant skipping capabilities	Qualcomm Incorporated, Nokia, Nokia Shanghai Bell
R2-2108735	Introducing UL MIMO coherence capability for Tx switching	ZTE Corporation, Sanechips
R2-2108736	Introducing UL MIMO coherence capability for Tx switching	ZTE Corporation, Sanechips
R2-2108756	Discussion on n77 issue	MediaTek Inc.
R2-2109163	Summary of [AT115-e][028][NR16] UE capabilities I	Huawei, HiSilicon
R2-2109168	LS on PDCCH Blind Detection in CA	RAN2
R2-2109178	Miscellaneous corrections to UE capability descriptions	Lenovo, Motorola Mobility
R2-2109182	Distinguishing support of extended band n77	Nokia, Nokia Shanghai Bell
R2-2109183	Distinguishing support of extended band n77	Nokia, Nokia Shanghai Bell
R2-2109184	Distinguishing support of extended band n77	Nokia, Nokia Shanghai Bell
R2-2109185	Distinguishing support of extended band n77	Nokia, Nokia Shanghai Bell
R2-2109186	[Draft] LS on inter-operability of band n77 extension in US	Nokia
R2-2109203	FR1/FR2 differentiation for enhanced UL grant skipping capabilities	Qualcomm Incorporated
R2-2109204	FR1/FR2 differentiation for enhanced UL grant skipping capabilities	Qualcomm Incorporated
R2-2109223	LS on inter-operability of band n77 extension in US	RAN2
6.1.4.4	Idle/inactive mode procedures
R2-2107088	Correction on RRM relaxation of higher priority frequencies	OPPO
R2-2107402	Discussion on LS from RAN4 on RRM relaxation in power saving	vivo, Huawei, HiSilicon, Qualcomm
R2-2107403	[Draft] Reply LS to RAN4 on RRM relaxation in power saving	vivo
R2-2108236	Addressing inconsistency for RRM measurement rules	Ericsson
R2-2108362	Clarification of access restrictions during cell re-selection	Qualcomm Incorporated
R2-2108841	Addressing inconsistency for RRM measurement rules	Ericsson, CATT
R2-2108877	Reply LS on RRM relaxation in power saving	RAN2
R2-2108909	LS on the MBS broadcast service continuity and MBS session identification	Huawei
R2-2109109	[AT115-e][030][NR15NR16] Idle Inactive (Qualcomm)	Qualcomm Incorporated
R2-2109112	Clarification of access restrictions during cell re-selection	Qualcomm Incorporated
6.2.1	General and Stage-2 corrections
R2-2106912	LS on RRC parameter for PSFCH RB set (R1-2106192; contact: LGE)	RAN1
6.2.2	Control plane corrections
R2-2107012	Corrections to usage of dynamic SL grants when T310 is running	Samsung Electronics Co., Ltd
R2-2107166	Miscelleneous CR on 38.331	Huawei, HiSilicon
R2-2107167	Miscelleneous CR on 36.331	Huawei, HiSilicon
R2-2107437	Correction on TS 38.331 from the latest RAN1 decisions	ZTE Corporation, Sanechips
R2-2108178	Corrections on RRC parameter PSFCH RB set	CATT
R2-2108218	Discussion on SL PDCP out-of-order delivery configuration	vivo
R2-2108219	CR on SL-SRB1 integrity check failure	vivo, Ericsson
R2-2108741	Correction on SL PDCP out-of-order delivery configuration	vivo
R2-2108985	Miscellaneous corrections on TS 38.331	Huawei, HiSilicon, CATT, ZTE Corporation, Sanechips, vivo, Ericsson
R2-2108986	Miscelleneous CR on 36.331	Huawei, HiSilicon
R2-2108987	Summary [AT115-e][705][V2X/SL] Miscellaneous CRs on RRC (Huawei)	Huawei, HiSilicon
R2-2108990	Summary of [AT115-e][706][V2XSL] SL PDCP out-of-order delivery configuration	vivo
R2-2108999	Miscellaneous corrections on TS 36.331	Huawei, HiSilicon
R2-2109024	Review report on RRC CRs	Huawei, HiSilicon
6.2.3	User plane corrections
R2-2107168	Corrections on the dynamic sidelink grants	Huawei, HiSilicon
R2-2107185	Correction on UL-SL prioritization	OPPO, Apple
R2-2107186	Correction on UL/SL prioritization	OPPO, Apple
R2-2107187	Correct on priority of MAC PDU for SL-SCH	OPPO
R2-2107188	Correction on random selection	OPPO
R2-2107189	Left issue on maxTransNum	OPPO
R2-2107302	Correction on condition of setting the resource reservation interval for mode 2	Sharp, ZTE Corporation, Sanechips, OPPO
R2-2107436	Correction on HARQ reporting on Uu	ZTE Corporation, Sanechips
R2-2108161	Review Report on MAC CRs	LG Electronics Inc.
R2-2108177	Corrections on MCS selection when UE performing TX resource (re-)selection check	CATT
R2-2108220	Correction on SR procedure for SL-CSI reporting	vivo, ZTE corporation
R2-2108221	Remaining issues on sl-MaxTransNum configuration and UE behaviour	vivo
R2-2108707	Corrections for SR configuration for SL	ASUSTeK
R2-2108991	Corrections on the dynamic sidelink grants	Huawei, HiSilicon
R2-2108992	Summary [AT115-e][707][V2X/SL] Corrections on the dynamic sidelink grants (Huawei)	Huawei, HiSilicon
R2-2108993	Correct on random selection	OPPO
R2-2108994	[AT115-e][709][V2X/SL] MAC discussion on remaining issues (LG)	LG Electronics Inc. (Rapporteur)
R2-2109000	[AT115-e][709][V2X/SL] MAC discussion on remaining issues (LG)	LG Electronics Inc. (Rapporteur)
R2-2109001	Correction on condition of setting the resource reservation interval for mode 2	Sharp, ZTE Corporation, Sanechips, OPPO
R2-2109002	Correction on SR procedure for SL-CSI reporting	vivo, ZTE corporation
6.3.1	General and Stage 2 corrections
R2-2107331	Correction to NRPPa PDU transfer for uplink positioning	Huawei, HiSilicon
R2-2107333	Correciton to NB-IoT positioning	Huawei, HiSilicon
R2-2107334	Correction to 38.305 on NG-RAN positioning operations	Huawei, HiSilicon
R2-2107958	Correction on user-plane positioning support by SUPL	Samsung, Qualcomm Incorporated
R2-2108410	PRS only TP for NR	Ericsson
R2-2109125	Correction on user-plane positioning support by SUPL	Samsung, Qualcomm Incorporated
6.3.2	RRC corrections
R2-2107960	Misalignment between RRC and NRPPa in SRS configuration	Samsung
R2-2107961	Relation between pathlossReference and spatialRelationInfo	Samsung
R2-2108935	LS to RAN3 on the misalignment in SRS configuration	RAN2
6.3.3	LPP corrections
R2-2107121	Correction for LPP assistance information	ROHDE & SCHWARZ
R2-2107227	Discussion on the presence tag for Uplink LPP message	CATT
R2-2107228	Corrections on the conditional presence tag clarification for Uplink LPP message	CATT
R2-2107229	Corrections on the conditional presence tag clarification for Uplink LPP message	CATT
R2-2107230	Miscellaneous correction on the description of RequestedMeasurements	CATT
R2-2107332	Correction to PRS-only TP	Huawei, HiSilicon
R2-2108363	Correction to the need code in NR-SelectedDL-PRS-IndexList	Qualcomm Incorporated
R2-2108404	on Need codes and PRS-only TP	Ericsson
R2-2108405	Correction of Need code for UE signalling of NR-TimeStamp	Ericsson
R2-2108406	Addition of PRS only TP	Ericsson
R2-2108808	Summary of agenda item 6.3.3 - REL-16 LPP Corrections	Nokia, Nokia Shanghai Bell
R2-2108936	Corrections on the conditional presence tag clarification for Uplink LPP message	CATT, Ericsson
R2-2108937	Correction to PRS-only TP	Huawei, HiSilicon
R2-2108951	[AT115-e][Offline-607][POS] PRS-only TP flag and other identifiers (Huawei)	Huawei, HiSilicon
R2-2108955	Correction to PRS-only TP	Huawei, HiSilicon, Ericsson
R2-2108956	Correction to PRS-only TP	Huawei, HiSilicon, Ericsson
R2-2109008	Correction to PRS-only TP	Huawei, HiSilicon, Ericsson
R2-2109047	Correction for LPP assistance information	Rohde & Schwarz
R2-2109207	Report of [606][POS] LPP need code guidelines for uplink (CATT)	CATT
6.4.1	General and stage-2 corrections
R2-2106979	LS Reply on QoS Monitoring for URLLC (S5-211350; contact: Intel)	SA5
R2-2108299	On UL delay configuration in LTE	Ericsson
R2-2108314	[Draft] Reply LS on MDT Stage 2 and Stage 3 alignment	Ericsson
R2-2108562	Draft Reply LS on QoS Monitoring for URLLC	Huawei
R2-2109145	Report of [Offline-887][SONMDT] On UL delay configuration in LTE (Ericsson)	Ericsson
R2-2109147	On UL delay configuration in LTE	Ericsson
6.4.2	TS 38.314 corrections
R2-2108304	On corrections to packet loss rate measurements	Ericsson
R2-2109146	Report of [Offline-886][SONMDT] On corrections to packet loss rate measurements (Ericsson)	Ericsson
R2-2109148	On corrections to packet loss rate measurements	Ericsson
6.4.3	RRC corrections
R2-2107586	CSI-RS reporting for RA in RLF	Apple
R2-2107587	Correction on clearing VarRA-Report	Apple
R2-2107819	Corrections on RLF Report Storage in 36.331	CATT, Huawei, HiSilicon
R2-2107820	Corrections on RLF Report Storage in 38.331	CATT, Huawei, HiSilicon
R2-2107854	Clarification on CGI-EUTRALogging	Samsung Electronics Co., Ltd
R2-2107863	Correction on logging for outOfCoverage event	Samsung, Ericsson
R2-2107864	Correction on inclusion of the set of availability indicators during RRC reconfiguration	Samsung Electronics Co., Ltd
R2-2108308	On OutOfCoverage related logging	Ericsson
R2-2108309	On PDCP queuing delay value measurement	Ericsson
R2-2108321	Correction to RLF reporting	QUALCOMM INCORPORATED
R2-2108358	Correction to 38331 on OOC event triggered logged MDT	ZTE Corporation, Sanechips
R2-2108359	Consideration on event triggered logged MDT	ZTE Corporation, Sanechips
R2-2108420	Corrections to previousPCellID and timeConnFailure handling	Ericsson
R2-2108561	Discussion on uplink delay value reporting	Huawei, HiSilicon
R2-2108563	Discussion on the user consent for trace reporting	Huawei, HiSilicon
R2-2108968	SON-MDT Changes agreed in RAN2#115 meeting	Ericsson, Huawei
7.1.1	Cross WI RRC corrections
R2-2107774	Correction on early security reactivation upon reception of RRCConnectionReject	NEC
7.2.1	General and Stage-2 corrections
R2-2106906	Reply LS on timing of neighbor cell RSS-based measurements (R1-2104033; contact: Qualcomm)	RAN1
R2-2106915	Reply LS on RSS based RSRQ for LTE-MTC (R1-2106215; contact: Huawei)	RAN1
7.2.2	Connection to 5GC corrections
R2-2107428	Introduction of an indication of RRC_INACTIVE support in SIB1	Huawei, HiSilicon
R2-2107454	Introduction of an indication of RRC_INACTIVE support in SIB1	Huawei, HiSilicon
R2-2107769	36304_Correction on paging resource determination	ZTE Corporation, Sanechips, Qualcomm Incorporated
R2-2108906	[AT115-e][401][eMTC R16] Indication of RRC_INACTIVE support in SIB1 (Huawei)	Huawei
R2-2108907	Report of [AT115-e][402][eMTC R16] Paging resource determination (ZTE)	ZTE (email discussion rapporteur)
R2-2108908	Correction on paging resource determination for eMTC UE in RRC_INACTIVE	ZTE Corporation, Sanechips, Qualcomm Incorporated
7.4	LTE Other WIs
R2-2108701	36.331 Correction on ReportConfigEUTRA for CHO/CPAC	CATT
R2-2108854	36.331 Correction on ReportConfigEUTRA for CHO/CPAC	CATT
7.5	LTE Positioning
R2-2107959	Correction on user-plane positioning support by SUPL	Samsung, Qualcomm Incorporated
R2-2108933	Summary of [AT115-e][603][POS] AI 7.5 LTE Positioning and Rel-16 stage 2 CRs	Qualcomm Incorporated
8.1.1	Organizational, Requirements, Scope and Architecture
R2-2107335	Discussion on lossless mobility support for NR MBS	ZTE, Sanechips
R2-2107547	NR Multicast and Broadcast Radio Bearer Architecture aspects	Qualcomm Inc
R2-2108037	General aspects for NR MBS	CHENGDU TD TECH LTD.
R2-2108204	Summary of e-mail discussion “[Post114-e][074][MBS] RRC running CR” and RRC open issues list	Huawei, HiSilicon
R2-2108205	38.331 running CR for NR MBS	Huawei, HiSilicon
R2-2108796	Discussion on MBS support on MRDC	Xiaomi Communications
R2-2108923	38.304 running CR for NR MBS	CATT
R2-2108926	38.321 running CR for NR MBS	OPPO
R2-2108970	38.331 running CR for NR MBS	Huawei, HiSilicon
R2-2108978	38.300 Running CR for MBS in NR	CMCC, Huawei
R2-2108979	Report from [Post115-e][069][MBS] 38300 Running CR (CMCC)	CMCC
8.1.2.1	Multicast Service Continuity
R2-2107032	Open Issues on Mobility of Delivery Mode 1	CATT, CBN
R2-2107033	PTM/PTP Switch	CATT
R2-2107048	Mobility and Service continuity for NR Multicast	MediaTek Inc.
R2-2107119	PTM PTP switch and reliability	MediaTek Inc.
R2-2107204	Service continuity for MBS due to handover	OPPO
R2-2107206	[Post114-e][072][MBS] Delivery Mode 1 PTM PTP operation (OPPO)	OPPO
R2-2107336	Multicast Service Continuity	ZTE, Sanechips
R2-2107363	Discussion on Multicast service continuity during mobility	Spreadtrum Communications
R2-2107539	L2 ARQ by PDCP for PTM	Futurewei, Qualcomm Inc., Intel, UIC, Kyocera, NEC, Samsung, Ericsson
R2-2107544	PDCP Functionality during Mobility and PTM-PTP Switch	Futurewei
R2-2107576	PTM and PTP switch with MBS service continuity	Apple
R2-2107657	PTP UM RLC configuration	Fujitsu
R2-2107685	Dynamic PTM PTP Switch	TCL Communication Ltd.
R2-2107690	MBS Reliability	Nokia, Nokia Shanghai Bell
R2-2107692	MBS Mobility	Nokia, Nokia Shanghai Bell
R2-2107693	Draft LS on MBS mobility	Nokia, Nokia Shanghai Bell
R2-2107697	Reliability of NR MBS	NEC
R2-2107702	MBS L2 reliability	NEC
R2-2107703	Service Continuity for Connected mode UE	NEC
R2-2107793	Service Continuity during Inter-cell mobility	vivo
R2-2107794	CHO and DAPS for NR MBS	vivo
R2-2107795	Discussion on PTP PTM Switch	vivo
R2-2107919	Discussion on MRB type change and PTM/PTP switch	Lenovo, Motorola Mobility
R2-2107921	Service Continuity for handover from MBS Supporting Node to MBS non-Supporting Node	Lenovo, Motorola Mobility
R2-2107932	Service Continuity for Multicast	Samsung
R2-2108000	Remaining issues of dynamic PTM - PTP switching and mobility for NR MBS	Kyocera
R2-2108032	Service continuity for delivery mode 1	CHENGDU TD TECH LTD.
R2-2108050	Need for L2 ARQ for PTM to PTP switch	Sony
R2-2108080	Reliability for Multicast and for Multicast Service Continuity	Ericsson
R2-2108124	Inter-cell mobility for MBS	Huawei, HiSilicon
R2-2108485	Lossless PTM/PTP switching	InterDigital
R2-2108519	Discussion on dynamic PTP/PTM switch	CMCC
R2-2108550	Discussion on multicast service continuity	LG Electronics Inc.
R2-2108676	Multicast service continuity in mobility and PTM/PTP switching	Intel Corporation
R2-2108708	UE stay in RRC_CONNECTED when no MBS data ongoing	ASUSTeK
R2-2108754	Activation and Deactivation of PTM/PTP leg	Convida Wireless
R2-2109022	Inter-cell mobility for MBS	Huawei, HiSilicon
8.1.2.2	Scheduling and power saving
R2-2107034	Discussion on Scheduling and Power Saving of MBS	CATT
R2-2107049	DRX scheme for NR MBS	MediaTek Inc.
R2-2107205	Discussion on group-based scheduling for MBS	OPPO
R2-2107233	MBS Power Saving and Scheduling Aspects	Samsung
R2-2107337	Group scheduling and power saving for NR MBS	ZTE, Sanechips
R2-2107438	Consideration on dynamic PTM and PTP switching for NR MBS	Shanghai Jiao Tong University
R2-2107439	Deactivation and reactivation of MBS reception	Shanghai Jiao Tong University
R2-2107446	MBS group scheduling and power saving	Intel Corporation
R2-2107467	Determination of HARQ retransmission for PTM	FGI, Asia Pacific Telecom
R2-2107545	NR Multicast DRX aspects	Qualcomm India Pvt Ltd
R2-2107577	DRX mechanism for MBS PTM reception	Apple
R2-2107682	DRX for PTM and PTP	TCL Communication Ltd.
R2-2107694	DRX for Multicast	Nokia, Nokia Shanghai Bell
R2-2107698	Service Continuity for Connected mode UE	NEC
R2-2107699	Simultaneous transmission of multicast/unicast	NEC
R2-2107787	Notification of the Activation/Deactivation of PTM	SHARP Corporation
R2-2107796	Further Considerations on Group Scheduling for MBS	vivo
R2-2107920	MBS specific DRX operation and Data Inactivity Monitoring	Lenovo, Motorola Mobility
R2-2107931	MBS Group Scheduling	Samsung
R2-2108002	Open issues on group scheduling for NR MBS	Kyocera
R2-2108033	Scheduling for NR MBS	CHENGDU TD TECH LTD.
R2-2108079	Aspects on Power Saving	Ericsson
R2-2108083	Aspects on Scheduling	Ericsson
R2-2108123	Support of dynamic switch	Huawei, HiSilicon
R2-2108125	Discussion on group scheduling	Huawei, HiSilicon
R2-2108479	Power saving for MBS PTM	ETRI
R2-2108486	PTM activation and deactivation	InterDigital
R2-2108520	Discussion on group scheduling	CMCC
R2-2108551	Discussion on group scheduling and power saving	LG Electronics Inc.
R2-2108798	Discussion on the group scheduling of MBS	Xiaomi Communications
R2-2108846	[Pre115-e][001][MBS] Summary 8.1.2.2 L2 Centric Scheduling and PowSav (Qualcomm)	Qualcomm
8.1.2.3	Other
R2-2107120	Initialization of RLC and PDCP windows	MediaTek Inc.
R2-2107338	Miscellaneous L2 centric issues on NR MBS	ZTE, Sanechips
R2-2107548	NR Multicast Broadcast mobility enhancements with service continuity	Qualcomm Inc
R2-2107797	PDCP and RLC Initialization for MBS Reception	vivo
R2-2107933	Layer-2 Aspects for MBS	Samsung
R2-2108040	CQI audit procedure for delivery mode 2	TD Tech
R2-2108082	Initialization of RLC and PDCP window	Ericsson
R2-2108126	Initialization of RLC and PDCP windows	Huawei, HiSilicon
R2-2108487	On RLC receiver state variables during PTM/PTP switching	InterDigital
R2-2108521	Discussion on MBS UP design	CMCC
R2-2108552	Discussion on MRB related issues and others	LG Electronics Inc.
R2-2108654	Discussion on MCCH	CHENGDU TD TECH LTD.
R2-2108797	Remaining PDCP issues for MBS	Xiaomi Communications
R2-2108809	Discussion on definition of PTM transmission considering HARQ for PTM	LG Electronics Inc.
R2-2109026	Summary of [Pre115-e][002] [MBS] 8.1.2.3 L2 Centric Other	MediaTek Inc.
8.1.3	L3 Centric
R2-2107696	IDLE /IN_ACTIVE UE support of MBS	NEC
8.1.3.1	Broadcast Service Continuity
R2-2107013	Discussion on MBS interesting indication for delivery mode 2	OPPO
R2-2107017	Discussion on MBS service continuity for delivery mode 2	OPPO
R2-2107035	Open Issues on Service Continuity of Delivery Mode 2	CATT, CBN
R2-2107050	Broadcast Service Continuity	MediaTek Inc.
R2-2107234	On Broadcast Service Continuity	Samsung
R2-2107339	Broadcast Service Continuity	ZTE, Sanechips
R2-2107364	Discussion on issues of delivery mode2	Spreadtrum Communications
R2-2107387	Discussion on Service Continuity Support for NR MBS	TCL Communication Ltd.
R2-2107798	Discussion on Broadcast Service Continuity	vivo
R2-2107875	MBS service continuity	LG Electronics Inc.
R2-2107981	MCCH considerations	Nokia, Nokia Shanghai Bell
R2-2107999	Details of control plane aspects for delivery mode 2 in NR MBS	Kyocera
R2-2108034	Service continuity for delivery mode 2	CHENGDU TD TECH LTD.
R2-2108081	Open issues in Broadcast Service Continuity	Ericsson
R2-2108201	Remaining issues of MBS Interest Indication	Huawei, HiSilicon
R2-2108522	Discussion on Broadcast service continuity issues	CMCC
R2-2108677	Service continuity for delivery mode 2	Intel Corporation
R2-2108799	Summary of [Post114-e][073][MBS] Service continuity for Delivery Mode 2 (Xiaomi)	Xiaomi Communications
R2-2108914	LS on the MBS broadcast service continuity and MBS session identification	RAN2
R2-2109041	Report of [AT115-e][047][MBS] Service Continuity deliver mode 2	Xiaomi Communications
R2-2109052	Report of [AT115-e][047][MBS] Service Continuity deliver mode 2	Xiaomi Communications
8.1.3.2	Notifications
R2-2107015	Discussion on MCCH change notification	OPPO
R2-2107016	Group notification and unicast paging for MBS activation	OPPO
R2-2107036	On Multicast Activation Notification	CATT, CBN
R2-2107037	Open Issues on MCCH Change Notification	CATT
R2-2107051	Notification for Multicast activation	MediaTek Inc.
R2-2107235	Considerations on Notifications for Multicast and Broadcast	Samsung
R2-2107340	Notifications for NR MBS	ZTE, Sanechips
R2-2107365	Discussion on multicast activation notification	Spreadtrum Communications
R2-2107530	Further discussion on the MBS group notification in DM2	Futurewei
R2-2107578	Access Control for the MBS Service Reception	Apple
R2-2107799	Discussion on MBS Notification and MCCH	vivo
R2-2107876	MCCH information acquisition	LG Electronics Inc.
R2-2107877	RRC connection establishmentresume initiated by group paging	LG Electronics Inc.
R2-2107922	Notification for Multicast activation	Lenovo, Motorola Mobility
R2-2107982	MBS session activation and group paging	Nokia, Nokia Shanghai Bell
R2-2108001	Group notification for Delivery mode 1 in NR MBS	Kyocera
R2-2108035	Discussion on notificatons for NR MBS	CHENGDU TD TECH LTD.
R2-2108078	Aspects on notification	Ericsson
R2-2108202	Notifications for Multicast and Broadcast	Huawei, HiSilicon
R2-2108455	Multicast activation notification and MCCH change notification	Intel Corporation
R2-2108523	Discussion MBS notification schemes	CMCC
R2-2108800	PRACH congestion due to multicast paging	Xiaomi Communications
R2-2108847	Summary 8.1.3.2 - L3 Centric Notifications (Samsung)	Samsung
R2-2109078	Report of [AT115-e][048][MBS] Notifications (Samsung)	Samsung
R2-2109177	LS on paging for multicast session activation notification	RAN2
8.1.3.3	Other
R2-2107014	Discussion on beam sweeping transmission for delivery mode 2	OPPO
R2-2107038	Discussion on MCCH Contents and General RRC Aspects	CATT, CBN
R2-2107052	MCCH Configuration	MediaTek Inc.
R2-2107236	MCCH Contents and RRC Aspects for MBS	Samsung
R2-2107341	MCCH contents for NR MBS	ZTE, Sanechips
R2-2107366	RRC issues of multicast session	Spreadtrum Communications
R2-2107529	Configurations for MRB and scheduling via MCCH in DM2	Futurewei
R2-2107531	Handling MBS during conditional handover	Futurewei
R2-2107546	NR MBS control signalling aspects for UEs in different RRC states	Qualcomm Inc
R2-2107579	MBS reception in CONNECTED state	Apple
R2-2107691	Miscellaneous Aspects of MBS Provisioning	Nokia, Nokia Shanghai Bell
R2-2108036	MBS related configuration for delivery mode 2	CHENGDU TD TECH LTD.
R2-2108049	MBS BWP UE capability and MBS resources	Sony
R2-2108084	Other aspects for MBS	Ericsson
R2-2108203	MCCH acquisition in RRC_CONNECTED state	Huawei, HiSilicon
R2-2108456	Details for MCCH design	Intel Corporation
R2-2109035	[Pre115-e][004][MBS] Summary 8.1.3.3 L3 Centric Other	Huawei, HiSilicon
R2-2109104	Report of offline: [AT115-e][049][MBS] L3 Other (Huawei)	Huawei, HiSilicon
8.2.1	Organizational, Requirements and Scope
R2-2106962	Reply LS on temporary RS for efficient SCell activation in NR CA (R4-2108364; contact: Huawei)	RAN4
R2-2108688	TS 37.340 CR for CPA and inter-SN CPC	CATT
8.2.2.1	Deactivation of SCG
R2-2107018	Discussion on SCG deactivation for RRC_INACTIVE UE	OPPO
R2-2107422	Deactivation of SCG	Qualcomm Incorporated
R2-2107663	DC power sharing for deactivated SCG	Samsung
R2-2107669	Bearer handling for SCG deactivation	Samsung
R2-2107983	Deactivation of SCG	Nokia, Nokia Shanghai Bell
R2-2108091	Deactivation of SCG	LG Electronics
R2-2108165	Details of SCG deactivation	China Telecommunications
R2-2108330	Comparison of SCG deactivation solutions	Convida Wireless
R2-2108388	Efficient SCG (de)activation	Ericsson
R2-2108444	[Post114-e][231][R17 DCCA] SCG activation/deactivation options (Huawei)	Huawei, HiSilicon
R2-2108445	Remaining issues on UE-requested SCG deactivation	Huawei, HiSilicon
R2-2108488	Deactivation of SCG	InterDigital
R2-2108530	Discussions on deactivation of SCG	CMCC
R2-2108678	UE Assistance Information for SCG deactivation	SHARP Corporation
R2-2108691	Discussion on Deactivation of SCG	CATT
R2-2108813	Discussion on deactivation of SCG	NTT DOCOMO INC.
R2-2108862	[AT115-e][220][R17 DCCA] Bearer handling of SCG deactivation (Samsung)	Samsung
R2-2108865	[AT115-e][223][R17 DCCA] Network-triggered SCG activation (Huawei)	Huawei
8.2.2.2	UE measurements and reporting in deactivated SCG
R2-2107020	UE measurements and reporting in SCG deactivation	OPPO
R2-2107328	UE behavior in deactivated SCG	NTT DOCOMO INC.
R2-2107423	UE measurements and reporting in deactivated SCG	Qualcomm Incorporated
R2-2107603	TA Maintenance and other RRM UE actions in SCG deactivated state	Apple
R2-2107746	Discussion on UE behaivour when SCG is deactivated	ZTE Corporation, Sanechips
R2-2107753	Mobility for deactivated SCG	NTT DOCOMO INC.
R2-2107923	UE behavior when SCG is deactivated	Lenovo, Motorola Mobility
R2-2108132	Further considerations on SCG deactivation	NEC
R2-2108166	Discussion on UE behavior in deactivated SCG	China Telecommunications
R2-2108389	UE measurements and reporting in deactivated SCG	Ericsson
R2-2108446	UE behaviour while the SCG is deactivated	Huawei, HiSilicon
R2-2108489	Measurements and maintenance of UL synch with a deactivated SCG	InterDigital
R2-2108649	Discussion for UE behaviour in deactivated SCG	SHARP Corporation
R2-2108669	UE behavior when SCG is deactivated	vivo
R2-2108692	UE Behavior in Deactivated SCG	CATT
R2-2108721	UE Measurements in SCG Deactivation	LG Electronics
R2-2108733	UE behavior during SCG deactivation	MediaTek Inc.
8.2.2.3	Activation of deactivated SCG
R2-2107019	Open issues for activation of deactivated SCG	OPPO
R2-2107353	Discussion on UE behaviour when SCG is deactivated	Spreadtrum Communications
R2-2107420	Activation of deactivated SCG	Qualcomm Incorporated
R2-2107532	Discussion on random access and UE initiation for SCG fast activation	Futurewei
R2-2107602	Remaining aspects related to RACH-less SCG activation	Apple
R2-2107604	UE initiation of SCG (de)activation request	Apple
R2-2107668	PHR issues for SCG activation	Samsung
R2-2107747	Consideration on UE triggered SCG activation	ZTE Corporation, Sanechips
R2-2107865	UL data handling in deactivated SCG	DENSO CORPORATION
R2-2107874	UL data handling in deactivated SCG	DENSO CORPORATION
R2-2107924	Discussion on SCG activation	Lenovo, Motorola Mobility
R2-2108133	Further discussions on SCG activation	NEC
R2-2108134	UE request for SCG activation	NEC
R2-2108447	Lower layer signalling for SCG (de)activation	Huawei, HiSilicon
R2-2108490	Activation of SCG	InterDigital
R2-2108531	Discussions on activation of deactivated SCG	CMCC
R2-2108668	Discussion on activation of a deactivated SCG	vivo
R2-2108693	Considerations on Activation of Deactivated SCG	CATT
R2-2108722	Activation of SCG	LG Electronics
R2-2108728	Discussion on SCG activation	SHARP Corporation
R2-2108864	Summary of [AT115-e][222][R17 DCCA] Activation of deactivated SCG (NN)	NN
8.2.2.4	Other aspects of SCG activation/deactivation
R2-2107605	SCG bearer handling for the SCG deactivation feature	Apple
R2-2108532	Considerations for fast MCG link recovery with deactivated SCG	CMCC
8.2.3.1	CPAC procedures from network perspective
R2-2107111	Considerations on SN-initiated CPC procedure	KDDI Corporation
R2-2107226	Discussion on SN initiated conditional PSCell change	NTT DOCOMO INC.
R2-2107404	Discussion on CPAC procedures from NW perspective	vivo
R2-2107421	CPAC procedures from network perspective	Qualcomm Incorporated
R2-2107460	Discussion on SN initiated inter-SN CPC	China Telecommunication
R2-2107525	On SN-initiated CPC and the working assumptions	Nokia, Nokia Shanghai Bell
R2-2107533	Remaining issues with SN initiated CPC	Futurewei
R2-2107925	Issues related to SN initiated inter-SN CPC	Lenovo, Motorola Mobility
R2-2108112	Network procedures and signalling for CPAC	Ericsson
R2-2108135	Signaling details of SN-initiated CPC	NEC
R2-2108162	Discussion on SN initiated inter-SN CPC	ZTE Corporation, Sanechips
R2-2108163	Further consideration on CPAC procedure	ZTE Corporation, Sanechips
R2-2108448	Source SN configuration update during CPC configuration	Huawei, HiSilicon
R2-2108449	Reply LS on inter-node message design	Huawei, HiSilicon
R2-2108694	Discussion on CPAC procedures from network perspective	CATT
R2-2108775	Further consideration on CPAC stage 2 flow, and remaining issues	Samsung Electronics
R2-2108863	[Draft] Reply LS on Conditional PSCell Addition/Change agreements	Ericsson
R2-2109215	Reply LS on Conditional PSCell Addition/Change agreements	RAN2
8.2.3.2	CPAC procedures from UE perspective
R2-2107405	Discussion on CPAC procedures from UE perspective	vivo
R2-2107594	Discussion on CPAC open issues	Apple
R2-2108113	UE procedures and signalling for CPAC	Ericsson
R2-2108689	TS 38.331 CR for CPA and inter-SN CPC	CATT
R2-2108690	TS 36.331 CR for CPA and inter-SN CPC	CATT
R2-2108695	Summary of [Post114-e][233][eDCCA] Uu Message design for CPAC(CATT)	CATT
R2-2108723	Enhancements for CPAC	LG Electronics
R2-2109091	Summary of [Post114-e][233][eDCCA] Uu Message design for CPAC(CATT)	CATT
8.2.3.3	Other CPAC aspects
R2-2107524	On CPAC Procedures and Further Functionalities	Nokia, Nokia Shanghai Bell
R2-2107871	Failure handling of Conditional PSCell Addition	DENSO CORPORATION
R2-2107926	Miscellaneous issues on CPAC	Lenovo, Motorola Mobility
R2-2108491	Coexistence of CHO and CPC	InterDigital, Nokia, Nokia Shanghai Bell,ZTE Corporation, Sanechips
R2-2108533	Combination of CPAC and CHO	CMCC
8.2.4	Temporary RS for SCell activation
R2-2107021	Discussion on TRS activation for fast SCell activation	OPPO
R2-2107984	MAC CE for scell activation and temporary RS	Nokia, Nokia Shanghai Bell
R2-2108450	On RAN4 LS on Temporary RS for SCell activation	Huawei, HiSilicon
8.3.1	Organizational, Requirements and Scope
R2-2106935	Reply LS on NAS-based busy indication (R3-212877; contact: ZTE)	RAN3
R2-2106970	Reply LS on NAS-based busy indication (S2-2105150; contact: Intel)	SA2
R2-2107300	[Draft] Reply LS on NAS-based busy indication	Intel Corporation
8.3.2	Paging collision avoidance
R2-2107326	Open Issues on Paging Collision Avoidance	CATT
R2-2107388	Solutions for paging collision	Qualcomm Incorporated
R2-2107855	Paging Collision avoidance	vivo
R2-2107974	Paging collision avoidance	Ericsson
R2-2108015	Definition and solution for paging collision, RRC Inactive, SI change	Lenovo Mobile Com. Technology
R2-2108119	Paging Collision Avoidance Open Issues	Huawei, HiSilicon
R2-2108724	Considerations on Paging Collision	LG Electronics
8.3.3	UE notification on network switching for multi-SIM
R2-2107025	Discussion on Configured Time for AS-based Solution	OPPO
R2-2107026	Further Consideration for Busy Indication	OPPO
R2-2107027	Interaction between AS-based and NAS-based Solution for Network Switching	OPPO
R2-2107237	Considerations on Busy Indication Approach	Samsung
R2-2107265	Analysis on AS-based solution and NAS-based solution	China Telecommunications
R2-2107301	NAS and AS procedures and their interaction for aperiodic gap request	Intel Corporation
R2-2107327	Open Issues on Network Switching	CATT
R2-2107459	Network switching with leaving RRC Connected State of Multi-SIM	China Telecommunication
R2-2107477	Network switching for Multi-USIM devices during dual connectivity	Samsung
R2-2107597	Signaling aspects of MUSIM Network Switching	Apple
R2-2107598	MUSIM Band Conflict-RRC Processing Delay-Caller ID Requirements	Apple
R2-2107781	Open issues on scheduling gap for network switching	NEC
R2-2107789	RAN Initiated Network switching with Leaving RRC_CONNECTED	SHARP Corporation
R2-2107791	Open Issues for MUSIM Network Switching	Charter Communications, Inc
R2-2107807	Further analysis on NAS level solutions for RRC-INACTIVE	Nokia, Nokia Shanghai Bell
R2-2107808	On switching notification solutions for MUSIM operation	Nokia, Nokia Shanghai Bell
R2-2107856	Open Issues on Switching Notification	vivo
R2-2107857	Summary of Switching message details	vivo
R2-2107891	Switching notification and busy indication	Lenovo, Motorola Mobility
R2-2107973	Discussion on switching procedure without leaving RRC_CONNECTED state	Ericsson
R2-2107975	Discussion on switching procedure for leaving RRC_CONNECTED state	Ericsson
R2-2108031	On coordinated switch from NW for MUSIM device	Huawei, HiSilicon
R2-2108051	Discussion on Busy Indication in Inactive State	Sony
R2-2108052	Discussion on AS based Leaving in MultiSIM	Sony
R2-2108075	Consideration on the busy indication at Inactive state	ZTE Corporation, Sanechips
R2-2108076	Interaction between AS-based solution and NAS-based solution for network switching	ZTE Corporation, Sanechips
R2-2108077	Summary of [Post114-e][243][MUSIM] Gap handling	ZTE Corporation, Sanechips
R2-2108121	On busy indication in RRC_INACTIVE	Huawei, HiSilicon
R2-2108182	Further consideration on the remaining issues of scheduling Gap	ZTE Corporation, Sanechips
R2-2108360	Busy Indication in Multi-SIM	Qualcomm Incorporated
R2-2108361	Leaving Connected state in Multi-SIM	Qualcomm Incorporated
R2-2108387	Discussion about the usage of the autonomous gap	Xiaomi Communications
R2-2108709	Interaction between NAS and AS for network switching	ASUSTeK
R2-2108725	Considerations on SIM Swithcing	LG Electronics
R2-2108726	Scheduling Gap Handling	LG Electronics
R2-2108732	Further discussion on switching message details	Samsung Electronics Co., Ltd
R2-2108737	Busy indication in INACTIVE mode	MediaTek Inc.
R2-2108755	Procedures for MSIM UE notification on network switching	Futurewei Technologies
R2-2108804	Signalling design on busy indication procedure	DENSO CORPORATION
R2-2108855	Reply LS on NAS-based busy indication	RAN2
R2-2108856	[Draft] Reply LS on NAS-based busy indication	Intel
R2-2108861	LS on gap handling for MUSIM	RAN2
8.3.4	Paging with service indication
R2-2107028	Paging with Service Indication	OPPO
R2-2107180	Further discussion on introduction of paging cause	China Telecommunications
R2-2107298	Solution analysis for supporting Multi-SIM paging cause	Intel Corporation
R2-2107349	Discussion on the transmission of paging cause	Spreadtrum Communications
R2-2107350	Supporting of Paging Cause Solution detection	Spreadtrum Communications
R2-2107379	Paging Prioritization	Qualcomm Incorporated
R2-2107809	Service type Indication in paging for LTE/EPC	Nokia, Nokia Shanghai Bell
R2-2107858	Introduction of Paging Cause	vivo
R2-2107928	Discussion on support of paging cause for Multi-USIM devices	Samsung Electronics Co., Ltd
R2-2107976	Introduction of a Paging cause indication	Ericsson
R2-2108074	Consideration on the Service Indication	ZTE Corporation, Sanechips
R2-2108101	Detailed methods of the paging cause support for MUSIM	Xiaomi Communications
R2-2108122	Discussion on the paging with service indication	Huawei, HiSilicon
R2-2108549	Discussion on paging service indication for MUSIM	Futurewei Technologies
R2-2108727	Support of Paging Cause	LG Electronics
R2-2108738	Paging with service indication	MediaTek Inc.
R2-2108857	Summary of [AT115-e][231][MUSIM] Paging with service indication (NN)	NN
8.4.1	Organizational
R2-2106948	LS to RAN2 on reduction of service interruption during intra-donor IAB-node migration (R3-212973; contact: AT&T)	RAN3
R2-2106950	LS on Inter-donor migration (R3-212981; contact: Samsung)	RAN3
R2-2107169	Updated Rel-17 IAB Workplan	Qualcomm Incorporated, Samsung (WI rapporteurs)
R2-2108911	Running CR of TS 38.340 for eIAB	Huawei, HiSilicon
R2-2108920	Running CR to 37.340 for eIAB	vivo
R2-2108929	Running CR to 38.331 on NR IAB enhancements	Ericsson
R2-2108930	Running CR of TS 38.340 for eIAB	Huawei, HiSilicon
R2-2108969	Running CR to 38.300 for eIAB	Qualcomm
R2-2109107	Report from [AT115-e][040][eIAB] Reply LS on reduction of service interruption for intra-donor migration (AT&T)	AT&T
R2-2109108	Reply LS to RAN3 on reduction of service interruption during intra-donor IAB-node migration	RAN2
R2-2109122	[Draft] Reply LS on inter-donor migration	Samsung
R2-2109143	Reply LS on inter-donor migration	RAN2
8.4.2	Enhancements to improve topology-wide fairness multi-hop latency and congestion mitigation
R2-2107063	Fairness Latency and Congestion	CATT
R2-2107113	Discussion on flow control for congestion mitigation	CANON Research Centre France
R2-2107177	Fairness, latency and congestion – solutions to identified issues	Samsung Electronics GmbH
R2-2107178	Enhancements to LCG space and BSR triggering including pre-emptive BSR	Samsung Electronics GmbH
R2-2107250	Enhancements for topology-wide fairness, multi-hop latency and congestion mitigation	Huawei, HiSilicon
R2-2107289	IAB topology-wide fairness, latency, and congestion enhancement	Intel Corporation
R2-2107635	Way forward for IAB enhancements to improve topology-wide fairness multi-hop latency and congestion mitigation	Apple
R2-2107851	An elaboration of required PDB for multi-hop latency	ITRI
R2-2107859	Discussion on multi-hop latency and LCG extension issues	vivo
R2-2107892	Discussion on LCG extension for IAB	Lenovo, Motorola Mobility
R2-2107998	Possible solutions for topology-wide fairness, multi-hop latency and congestion mitigation in eIAB	Kyocera
R2-2108053	Number of hops information to improve topology-wide fairness and latency	Sony
R2-2108139	Discussion on fairness, multi-hop latency and congestion mitigation	ZTE, Sanechips
R2-2108241	Fairness, latency, congestion	Nokia, Nokia Shanghai Bell
R2-2108421	On Topology-wide Fairness, Multi-hop Latency, and Congestion in IAB Network	Ericsson
R2-2108437	Multi-hop scheduling enhancements for IAB	AT&T
R2-2108492	Timing information for latency enhancement in multi-hop IAB	InterDigital
R2-2108493	Latency enforcement, fairness and congestion mitigation in multi-hop IAB	InterDigital
R2-2108743	Discussion on topology-wide fairness, multi-hop latency and congestion mitigation	LG Electronics Inc.
R2-2108753	Rel. 17 IAB enhancements for fairness, multi-hop latency reduction, and congestion mitigation	Futurewei Technologies
R2-2109032	Feature summary of 8.4.2 (Rel-17 IAB contributions on fairness, latency and congestion)	InterDigital
R2-2109106	Report of [AT115-e][042][eIAB] fairness, latency and congestion (Interdigital=	Interdigital (rapporteur)
8.4.3	Topology adaptation enhancements
R2-2107064	Remaining issue of Local Rerouting	CATT
R2-2107065	On Two Logical IAB-DUs in Boundary IAB-node	CATT
R2-2107066	Reducing Service Interruption during Intra-donor IAB-node Migration	CATT
R2-2107112	Discussion on BH Link issue detection	CANON Research Centre France
R2-2107114	Discussion on inter-donor DU local re-routing	CANON Research Centre France
R2-2107115	Discussion on RLF indication enhancements	CANON Research Centre France
R2-2107170	BAP-layer traffic processing at the boundary node	Qualcomm Incorporated
R2-2107171	Discussion of RAN3 LS on Interruption time reduction for Intra-donor IAB-node Migration	Qualcomm Incorporated, Apple
R2-2107172	RAN2 aspects related to RAN3’s LS on Full Migration	Qualcomm Incorporated, Apple
R2-2107179	Triggers for local rerouting	Samsung Electronics GmbH
R2-2107251	Summary of [Post114-e][075][eIAB] Open Issues on Re-routing	Huawei, HiSilicon
R2-2107252	Discussion on two logical DUs and service interruption reduction for RAN3 LS	Huawei, HiSilicon
R2-2107253	Inter-donor routing, local rerouting and RLF indication for R17-IAB	Huawei, HiSilicon
R2-2107254	F1 over NR access link and CHO	Huawei, HiSilicon
R2-2107290	IAB dual connection, RLF and local rerouting	Intel Corporation
R2-2107291	Intra-donor CU topology migration	Intel Corporation
R2-2107445	Inter-donor CU Topology migration	Intel Corporation
R2-2107516	Re-routing ehnancements and RLF indications in IAB	Nokia, Nokia Shanghai Bell
R2-2107517	Inter-donor-DU rerouting	Nokia, Nokia Shanghai Bell
R2-2107518	Analysis of RAN3 LS on Inter-donor migration	Nokia, Nokia Shanghai Bell
R2-2107636	Topology adaptation and RLF handling in eIAB networks	Apple
R2-2107648	Open issues on (re-)routing	Fujitsu
R2-2107649	Open issues on Type-2 BH RLF indication	Fujitsu
R2-2107650	Reduction of service interruption	Fujitsu
R2-2107651	UE handover during inter-donor-CU migration	Fujitsu
R2-2107695	Topology optimization in IAB	NEC
R2-2107700	DAPS-like handover and NR DC for IAB	NEC
R2-2107701	CHO for IAB	NEC
R2-2107860	Miscellaneous issues on topology adaptation	vivo
R2-2107861	On Inter-CU routing, Inter-donor-DU rerouting and local re-routing	vivo
R2-2107862	Discussion on Migration and Service Interruption	vivo
R2-2107893	Discussion on local rerouting and local bearer remapping for IAB	Lenovo, Motorola Mobility
R2-2107894	CHO recovery in IAB	Lenovo, Motorola Mobility
R2-2107997	BH RLF Indications and local rerouting for eIAB	Kyocera
R2-2108026	Topology adaptation enhancements	Samsung
R2-2108054	Introduce cost factor in local re-routing	Sony
R2-2108140	Discussion on inter-donor migration and service interruption reduction	ZTE, Sanechips
R2-2108141	Discussion on inter-donor topology redundancy	ZTE, Sanechips
R2-2108142	Discussion on RLF indication and local re-routing	ZTE, Sanechips
R2-2108416	Support for inter-donor-DU rerouting	Qualcomm Finland RFFE Oy
R2-2108422	Boundary IAB node behaviour for partial and full inter-donor migration	Ericsson
R2-2108423	On Intra-donor Migration: Reduction of service interruption and CHO	Ericsson
R2-2108424	On Local Routing and Type 2/3 RLF Handling	Ericsson
R2-2108438	Alternatives for full inter-donor migration	AT&T
R2-2108482	Solutions for Inter-Donor Routing and Bearer Mapping	Futurewei Technologies
R2-2108483	Enhancements to Rel. 17 IAB RLF indications and local routing	Futurewei Technologies
R2-2108494	CHO in IAB	InterDigital
R2-2108495	DAPS support in IAB	InterDigital
R2-2108657	Open issues on BH RLF indications	LG Electronics
R2-2108658	CHO and DAPS-like Solution for eIAB	LG Electronics
R2-2108744	Discussion on local routing, LCG extension, and CP-UP separation	LG Electronics Inc.
R2-2108873	Reply LS on inter-donor-DU rerouting	RAN2
8.5.1	Organizational
R2-2108019	Summary of Email Discussion [Post114-e][509][URLLC/IIoT] Running Stage 2 CR review (Nokia)	Nokia, Nokia Shanghai Bell
R2-2108020	Stage-2 Running CR for Rel-17 IIoT/URLLC	Nokia, Nokia Shanghai Bell
8.5.2	Enhancements for support of time synchronization
R2-2107116	Triggered Synchronization Activation	CANON Research Centre France
R2-2107152	Discussion about time synchronization enhancements	Huawei, HiSilicon
R2-2107528	RE: LS on Time Synchronization	IEEE 1588 WG
R2-2107556	Propagation Delay Compensation for TSN	Qualcomm Incorporated
R2-2107736	Consideration on the support of time synchronization enhancement	OPPO
R2-2107741	Remaining issues on time synchronization and PDC	ZTE Corporation, Sanechips, China Southern Power Grid Co., Ltd
R2-2107800	Discussion on propagation delay compensation	vivo
R2-2107897	Left issues for propagation delay compensation	Lenovo, Motorola Mobility
R2-2108021	Time Synchronization Signalling	Nokia, Nokia Shanghai Bell
R2-2108097	Summary of PDC Issues	Ericsson
R2-2108168	Discussion on RAN enhancement to support propagation delay compensation	China Telecommunications
R2-2108258	Issues on Propagation Delay Compensation	Samsung
R2-2108296	Report of email discussion [Post114-e][512][URLLC/IIoT] T-synch open issues (Intel)	Intel Corporation
R2-2108436	Leftover aspects on Timing Synchronization	Intel Corporation
R2-2108547	Support of time synchronization for TSN based on RAN1 progress	CMCC
R2-2108553	Discussion on enhancements for support of time synchronization	LG Electronics Inc.
R2-2108793	Discussion on the PDC support for IDLE or CONNECTED	Xiaomi Communications
R2-2108803	Timing synchronization for UE in RRC_INACTIVE state and RRC_IDLE state	TCL Communication Ltd.
R2-2108815	Discussion on uplink time synchronization for TSN	NTT DOCOMO, INC.
8.5.3	Uplink enhancements for URLLC in unlicensed controlled environments
R2-2107153	Remaining issues about Uplink enhancements for URLLC in UCE	Huawei, HiSilicon
R2-2107201	Sequential processing of autonomous retransmission and lch-based prioritization	CATT
R2-2107202	Time-based HPID for gNB-scheduled dynamic retransmissions	CATT
R2-2107557	CG Harmonization for Unlicensed Controlled Environment	Qualcomm Incorporated
R2-2107737	Consideration on URLLC over NR-U	OPPO
R2-2107801	Remaining issues about autonomous re-transmission	vivo
R2-2107896	Further details on enhancements for URLLC in UCE	Lenovo, Motorola Mobility
R2-2108022	Remaining Issues of URLLC in NR-Unlicensed	Nokia, Nokia Shanghai Bell
R2-2108098	Harmonizing UL CG enhancements in NR-U and URLLC	Ericsson
R2-2108231	Summary of [Post114-e][510][URLLC/IIoT] Open issues for UCE	MediaTek Inc.
R2-2108270	Further Consideration On the URLLC transmission in UCE	ZTE Corporation
R2-2108667	IIoT operation in unlicensed controlled environment	InterDigital
R2-2108674	Uplink enhancements for URLLC in unlicensed controlled environments	Intel Corporation
R2-2108748	Remaining issues of harmonizing UL CG enhancements for IIoT in UCE	III
R2-2108758	Issues on Prioritization in UCE	Samsung
R2-2108794	Remaining issues of CG harmonization	Xiaomi Communications
R2-2108810	Retransmission of UCI-only MAC PDU	LG Electronics UK
R2-2108825	Summary of AI 8.11.3 for RRC_INACTIVE positioning	ZTE
8.5.4	RAN enhancements based on new QoS
R2-2107154	Discussion on two-level PERs for survival time handling	Huawei, HiSilicon
R2-2107173	Report from email discussion [Post114-e][511][URLLC/IIoT] QoS Solutions (Samsung)	Samsung Electronics GmbH
R2-2107174	Entering, operating in, and exiting the Survival Time state	Samsung Electronics GmbH
R2-2107203	UE-based reactive solution for survival time	CATT
R2-2107558	RAN Enhancement to support Survival Time	QUALCOMM Europe Inc. - Italy
R2-2107611	Reliability enhancements for CG/SPS	Apple
R2-2107612	Further considerations on survival time for new QoS	Apple
R2-2107658	L1/L2 configuration adaptation	Fujitsu
R2-2107738	Consideration on RAN enhancement based on new QoS	OPPO
R2-2107742	Remaining issues on enhanced QoS	ZTE Corporation, Sanechips, China Southern Power Grid Co., Ltd
R2-2107802	Consideration on reactive solution for survival time	vivo
R2-2107806	Further discussions on RAN enhancements based on Survival Time	III
R2-2107895	Discuss on the mechanism to guarantee the survival time	Lenovo, Motorola Mobility
R2-2108023	Analysis of Potential RAN Enhancements for Survival Time	Nokia, Nokia Shanghai Bell
R2-2108099	RAN enhancements based on new QoS related parameters	Ericsson
R2-2108169	Discussion on RAN enhancement to support new QoS	China Telecommunications
R2-2108435	UE-based Survival time handling	Intel Corporation
R2-2108457	ST handling with alternating CC allocations	Sequans Communications
R2-2108459	Discussion on avoiding prematurely entering Survival Time state	Futurewei Technologies
R2-2108516	Discussion on the RAN support for new QoS parameters	CMCC
R2-2108666	Enhancements based on new QoS requirements	InterDigital
R2-2108786	Progress of QoS	LG Electronics UK
R2-2108795	Clarification on the survival time requirement	Xiaomi Communications
8.6.1	Organizational
R2-2106923	LS on the physical layer aspects of small data transmission (R1-2106335; contact: ZTE)	RAN1
R2-2106931	Reply LS on small data transmission (R3-212820; contact: Ericsson)	RAN3
R2-2107478	RRC Running CR for SDT	ZTE Corporation (rapporteur)
R2-2107486	Summary: [Post114-e][505][SData] RRC/MAC modeling and RRC running CR (ZTE)	ZTE Corporation (Rapporteur)
R2-2107494	Running MAC CR for small data	Huawei, HiSilicon
R2-2107495	Remaining issue for MAC spec	Huawei, HiSilicon
R2-2107496	Summary of [Post114-e][506][SData] Running MAC CR (Huawei)	Huawei, HiSilicon
R2-2108242	Stage-2 running CR Introduction of SDT	Nokia, Nokia Shanghai Bell
R2-2109065	Reply LS on Small data transmissions (S3-213034; contact: InterDigital)	SA3
8.6.2	User plane common aspects
R2-2107002	User Plane Common Aspects of RACH and CG based SDT	Samsung Electronics Co., Ltd
R2-2107053	Further Discussion on User Plane Aspect for Small Data Transmission	vivo
R2-2107055	Handling of non-SDT Data Arrival	vivo
R2-2107245	Discussion on the remianing issues of SDT modelling	OPPO
R2-2107246	Discussion on user plane issues of SDT	OPPO
R2-2107295	User Plane leftover issues on SDT mechanism	Intel Corporation
R2-2107464	Switching during a SDT procedure	FGI, Asia Pacific Telecom
R2-2107487	Common aspects for UP for SDT	ZTE Corporation, Sanechips
R2-2107778	User plane aspects of SDT	NEC
R2-2107844	User plane aspects of small data transmission	InterDigital, Europe, Ltd.
R2-2107898	The UP common issues for small data transmissions	Lenovo, Motorola Mobility
R2-2107991	UP common aspects of SDT	Qualcomm Incorporated
R2-2108055	User Plane aspects of SDT in NR	Sony
R2-2108087	Common aspects for SDT	Ericsson
R2-2108200	User plane common aspects for SDT	Huawei, HiSilicon
R2-2108508	UP common issues of SDT	CMCC
R2-2108680	Consideration on PDCP protocol in SDT	CATT
R2-2108681	Consideration on UP common aspects of SDT	CATT
R2-2108710	BSR and PHR for SDT procedure	ASUSTeK
R2-2108729	Remaining untreated proposals from [AT113bis-e][501] UP SDT open issues	LG Electronics Inc. (Rapporteur)
R2-2108730	Remaining UP issues in SDT	LG Electronics Inc.
R2-2108788	Discussion on the data volume computation	Xiaomi Communications
R2-2108789	Handling of MAC CE	Xiaomi Communications
R2-2109039	[Pre115-e][501][SData] Summary of 8.6.2 User Plane remaining open issues	LG Electronics Inc. (Rapporteur)
R2-2109079	[AT115-e][501][SData] Summary of UP SDT open issues	LG Electronics Inc. (Rapporteur)
R2-2109222	LS on agreements related to SDT	RAN2
8.6.3	Control plane common aspects
R2-2107003	Control Plane Common Aspects of RACH and CG based SDT	Samsung Electronics Co., Ltd
R2-2107054	Discussion on RRC-Controlled Small Data Transmission	vivo
R2-2107247	Discussion on control plane issues of SDT	OPPO
R2-2107292	Report of email discussion [Post114-e][507][SData] Non-SDT data arrival handling	Intel Corporation
R2-2107293	Control Plane leftover issues on SDT mechanism	Intel Corporation
R2-2107294	Expected duration and applicable features for SDT procedure	Intel Corporation
R2-2107463	Issues of the Subsequent Data Transmission	FGI, Asia Pacific Telecom
R2-2107488	Common aspects for CP for SDT	ZTE Corporation, Sanechips
R2-2107491	Control plane common aspects for SDT	Huawei, HiSilicon
R2-2107493	Discussion on the NAS aspects of Small Data	Huawei, HiSilicon
R2-2107580	Power Saving for SDT	Apple
R2-2107581	Non-SDT handling during the SDT procedure	Apple
R2-2107582	Control plane aspects on the SDT procedure	Apple
R2-2107659	Handling of SDTF detection timer	Fujitsu
R2-2107660	RAN paging reception and response during SDT	Fujitsu
R2-2107779	Control plane aspects of SDT	NEC
R2-2107866	Consideration on switching to non-SDT procedure	LG Electronics Inc.
R2-2107868	Consideration on security issue on CCCH-based approach	LG Electronics Inc.
R2-2107899	Discussion on CP data transmission over SDT	Lenovo, Motorola Mobility
R2-2107992	CP common aspects of SDT	Qualcomm Incorporated
R2-2108006	Discussion on some FFSes	Potevio Company Limited
R2-2108009	Paging reception during SDT	Nokia, Nokia Shanghai Bell
R2-2108056	Discussion on subsequent SDT in NR	Sony
R2-2108088	SDT Faliure Handling	Ericsson
R2-2108089	CP aspects for SDT	Ericsson
R2-2108261	SDT control plane aspects	Nokia, Nokia Shanghai Bell
R2-2108262	RRC procedure for SDT	Nokia, Nokia Shanghai Bell
R2-2108327	SDT cell re-selection	Convida Wireless
R2-2108506	Consideration on control plane issues	CMCC
R2-2108591	Paging reception during SDT	Nokia, Nokia Shanghai Bell
R2-2108665	Untreated proposal from [Post113-e][503]	InterDigital
R2-2108682	Consideration on CP issues	CATT
R2-2108731	Non-SDT data arrival handling	LG Electronics Inc.
R2-2108790	Paging reception during SDT	Xiaomi Communications
R2-2108816	Handling of abrupt termination for SDT	ZTE Wistron Telecom AB
8.6.4	Aspects specific to RACH based schemes
R2-2107004	RACH configuration for Small Data Transmission.	Samsung Electronics Co., Ltd
R2-2107005	Further Details of RACH bsaed Small Data Transmission	Samsung Electronics Co., Ltd
R2-2107056	Supporting Small Data Transmission via RA Procedure	vivo
R2-2107248	Discussion on RACH-based SDT	OPPO
R2-2107296	RACH leftover issues on SDT mechanism	Intel Corporation
R2-2107354	Discussion on RACH-based SDT	Spreadtrum Communications
R2-2107465	PDCCH monitoring in RA-SDT	FGI, Asia Pacific Telecom
R2-2107489	Open issues for RA-SDT	ZTE Corporation, Sanechips
R2-2107583	RACH specific SDT procedure	Apple
R2-2107780	Aspects specific to RACH based schemes	NEC
R2-2107993	Open issues for RACH based SDT	Qualcomm Incorporated
R2-2108057	Discussion on context fetch and anchor relocation	Sony
R2-2108058	RACH-based SDT in NR	Sony
R2-2108085	RACH based small data transmission	Ericsson
R2-2108199	Small data transmission with RA-based schemes	Huawei, HiSilicon
R2-2108243	Details of RACH specific schemes	Nokia, Nokia Shanghai Bell
R2-2108507	Discussion on RA-SDT	CMCC
R2-2108683	Transition from SDT to RRC_CONNECTED	CATT
R2-2108702	Discussion on RA-based small data transmission	Google Inc.
R2-2108711	Discussion on fallback to non-SDT	ASUSTeK
R2-2108712	Discussion on PDCCH monitoring for RA-SDT	ASUSTeK
R2-2108713	Discussion on RA configuration reception	ASUSTeK
R2-2108916	Report of [AT115e][502][SData] Summary of RA aspects	OPPO (Rapporteur)
8.6.5	Aspects specific to CG based schemes
R2-2107006	Details of Configured Grant based Small Data Transmission	Samsung Electronics Co., Ltd
R2-2107057	Supporting Small Data Transmission via CG PUSCH	vivo
R2-2107249	Discussion on CG-based SDT	OPPO
R2-2107297	CG-SDT leftover aspects	Intel Corporation
R2-2107440	Discussion on CG-SDT Request by UE	NEC Telecom MODUS Ltd.
R2-2107490	Open issues for CG-SDT	ZTE Corporation, Sanechips
R2-2107492	CG-based schemes for SDT	Huawei, HiSilicon
R2-2107584	CG specific SDT procedure	Apple
R2-2107661	PDCCH monitoring and SDT-TAT	Fujitsu
R2-2107788	Discussion on beam selection aspect for CG-SDT	PANASONIC R&D Center Germany
R2-2107850	CG-based SDT selection and configuration	InterDigital, Europe, Ltd.
R2-2107867	Consideration on open issues of CG-SDT	LG Electronics Inc.
R2-2107900	Consideration on CG based small data transmission	Lenovo, Motorola Mobility
R2-2107930	Report of [Post114-e][508][SData] Open issues for CG-SDT	Qualcomm Incorporated
R2-2107994	Open issues for CG based SDT	Qualcomm Incorporated
R2-2108010	Aspects specific to CG based SDT	Nokia, Nokia Shanghai Bell
R2-2108059	CG-based SDT in NR	Sony
R2-2108086	Details of CG based SDT	Ericsson
R2-2108509	Consideration on CG-SDT	CMCC
R2-2108630	Discussion on CG small data transmission	Google Inc.
R2-2108684	Analysis and views on CG-SDT	CATT
R2-2108714	Discussion on CS-RNTI for CG-SDT	ASUSTeK
R2-2108791	RACH failure in subsequent data transmission phase	Xiaomi Communications
R2-2108792	Remaining issues of CG SDT in RAN2	Xiaomi Communications
8.7.1	Organizational
R2-2106967	LS on RAN dependency issues for 5G ProSe (S2-2104932; contact: CATT)	SA2
R2-2106973	Reply LS on R17 Layer-2 SL Relay of UE ID exposure in paging mechanism (S3-212204; contact: Huawei)	SA3
R2-2107043	Stage 2 Running CR on Introduction of R17 SL Relay	MediaTek Inc.
R2-2107192	Work planning for R17 SL relay	OPPO
R2-2107193	Discussion on RAN2 impact from S2-2104932	OPPO
R2-2107755	Discuss SA2 LS on RAN dependency issues for 5G ProSe	vivo
R2-2108150	Draft LS reply on RAN dependency issues for 5G ProSe	ZTE, Sanechips
R2-2108179	[Dratf] LS reply on RAN depandency issues	CATT
R2-2108180	Discussion on LS reply on RAN depandency issues	CATT
R2-2108181	Corrections on ARP SDU Type in Rel-17	CATT
R2-2108194	Running CR of 38.304 for SL relay	Ericsson (Rapporteur)
R2-2108627	RRC running CR for SL relay	Huawei, HiSilicon
R2-2108675	Draft Relay LS on RAN dependency issues for 5G ProSe	Qualcomm Incorporated
R2-2108924	Introduction of Rel-17 Sidelink Relay	MediaTek Inc.
R2-2108938	Reply LS on RAN dependency issues for 5G ProSe	CATT
R2-2109124	Reply LS on RAN dependency issues for 5G ProSe	RAN2
R2-2109127	Reply LS on RAN dependency issues for 5G ProSe	RAN2
8.7.2.1	Control plane procedures
R2-2106989	Control Plane Procedures of L2 Relay	CATT
R2-2106990	PO Monitoring for Relay UE in RRC_CONNECTED and Remote UE in RRC_IDLE/RRC_INACTVE	CATT
R2-2107039	Discussion on Control Plane Aspects for L2 Relay	OPPO
R2-2107044	Stage 2 level procedure for Connection Establishment	MediaTek Inc.
R2-2107045	Remote UE Paging handling for connected Relay UE	MediaTek Inc.
R2-2107103	Further discussion on RRC connection management of L2 U2N relay	Qualcomm Incorporated
R2-2107104	Further discussion on paging and SIB forwarding in L2 U2N relay	Qualcomm Incorporated
R2-2107176	Remaining issues on RRC connection management	Samsung Electronics GmbH
R2-2107231	Discussion on RRC connection management for L2 sidelink relay	Huawei, HiSilicon
R2-2107232	SI forwarding and paging for L2 sidelink relay	Huawei, HiSilicon
R2-2107273	Connection Establishment Procedure for L2 UE to NW Relays	InterDigital
R2-2107274	Paging Procedures for L2 UE to NW Relays	InterDigital
R2-2107275	SI Forwarding for L2 UE to NW Relays	InterDigital
R2-2107304	Discussion on paging forwarding for a remote UE	SHARP Corporation
R2-2107306	Remaining issues of L2 Relay connection management	Intel Corporation
R2-2107367	Discussion on control plane procedures for L2 U2N relay	Spreadtrum Communications
R2-2107541	Configuration of Uu Interface for Sidelink Relay	Futurewei
R2-2107622	Remaining issues on SIB forwarding for IDLE/INACTIVE remote UE	Apple
R2-2107623	Unified Access Control on Relay UE	Apple
R2-2107625	RNA Update via L2 UE-to-NW relay	Apple
R2-2107708	SI message forwarding in L2 U2N relay	Samsung
R2-2107709	Paging delivery via L2 Relay in RRC_CONNECTED	Samsung
R2-2107756	Summary of [Post114-e][605][Relay] SI and paging forwarding (vivo)	vivo
R2-2107757	Way forward for L2 U2N Remote UE SRB0 SRB1 configuration	vivo
R2-2107966	Discussion on SI and paging delivery	Xiaomi communications
R2-2107967	Discussion on connection control	Xiaomi communications
R2-2108007	SI acquisition, CN Registration and RNAU	Lenovo Mobile Com. Technology
R2-2108008	Monitoring Paging by a U2N Relay	Lenovo Mobile Com. Technology
R2-2108060	L2 relay control plane procedures	Sony
R2-2108145	Consideration on the connection management of SL relay	ZTE, Sanechips
R2-2108146	Consideration on the system information acquisition and paging in SL relay	ZTE, Sanechips
R2-2108153	SIB Delivery & Paging for Remote UE	LG Electronics Inc.
R2-2108154	Connection Establishment	LG Electronics Inc.
R2-2108156	Relay reselection when Relay UE performs HO	LG Electronics Inc.
R2-2108192	Discussion on paging and SIB handling for L2 sidelink relay	Ericsson
R2-2108195	Discussion on RRC connection management procedures for L2 SL relay	Ericsson
R2-2108414	Discussion on SI and paging forwarding	ETRI
R2-2108458	Discussion on RRC connection establishment of remote UE in L2 U2N relay	Nokia, Nokia Shanghai Bell
R2-2108462	Support of idle mode mobility for remote-UE in SL UE-to-Nwk relay	Nokia, Nokia Shanghai Bell
R2-2108510	Control plane procedure	CMCC
R2-2108734	Leftover issues for SI delivery in L2 Relay	Intel Corporation
R2-2108820	Discussion on SI reception before establishing PC5-RRC connection	MediaTek Inc.
R2-2108824	Summary of AI 8.7.2.1	Xiaomi Technology
R2-2108948	Report of [Offline-616]	Xiaomi
8.7.2.2	Service continuity
R2-2106991	Service Continuity for L2 U2N Relay	CATT
R2-2107046	Stage 2 level procedure for Service Continuity	MediaTek Inc.
R2-2107106	Further discussion on Service continuity of L2 U2N relay	Qualcomm Incorporated
R2-2107196	Left issues on UP aspects for service continuity	OPPO
R2-2107213	Discussion on CP of NR sidelink relay service continuity	OPPO
R2-2107276	Service Continuity for L2 UE to NW Relays	InterDigital
R2-2107309	Open aspects of Service continuity support for L2 U2N relaying	Intel Corporation
R2-2107452	Remaining Issues on Service Continuity in L2 relaying	vivo
R2-2107540	Open Issues in Switches between Direct and Indirect Paths	Futurewei
R2-2107621	Discussion on service continuity for Layer 2 UE-to-NW relay	Apple
R2-2107710	Remaining easy proposals in outcome of [AT114-e][605][Relay]	Samsung(email discussion rapporteur)
R2-2107711	Remaining issues in Remote UE path switch procedures	Samsung
R2-2107887	Path switching in L2 U2N relay case	Lenovo, Motorola Mobility
R2-2107888	Service continuity with relay reselection	Lenovo, Motorola Mobility
R2-2107949	L2 Relay handover to non-L2-Relay capable gNB	Nokia, Nokia Shanghai Bell
R2-2107965	Discussion on service continuity	Xiaomi communications
R2-2108061	Service continuity open issues in L2 NR sidelink rela	Sony
R2-2108147	Discussion on the service continuity of SL relay	ZTE, Sanechips
R2-2108155	Relay (re)selection for service continuity	LG Electronics Inc.
R2-2108157	Measurement and report for path switching	LG Electronics Inc.
R2-2108193	Discussion on service continuity for L2 sidelink relay	Ericsson
R2-2108196	Feature summary for AI 8.7.2.2.	Ericsson
R2-2108282	Remaining issues on service continuity of SL relay	China Telecommunications
R2-2108322	Open issues on service continuity for relaying	Kyocera
R2-2108464	Handover interruption time reduction using sidelink communication	Nokia, Nokia Shanghai Bell
R2-2108513	Service continuity for L2 relay	CMCC
R2-2108622	Discussion on service continuity for L2 UE to NW Relay	Huawei, HiSilicon
R2-2108939	Email Report of [AT115-e][609][Relay] Service continuity procedures	MediaTek Inc. (Email Discussion Rapporteur)
8.7.2.3	Adaptation layer design
R2-2106992	Adaption Layer Design for L2 U2N Relay	CATT
R2-2107047	Adaptation layer for PC5 at L2 UE-to-Network Relay	MediaTek Inc., InterDigital
R2-2107105	Further discussion on adaptation layer of L2 U2N relay	Qualcomm Incorporated
R2-2107175	Open issues with Adaptation layer design	Samsung Electronics GmbH
R2-2107194	Left issues on CP aspects for adaptation layer	OPPO
R2-2107195	Left issues on UP aspects for adaptation layer	OPPO
R2-2107277	Discussion on L2 Relay Architecture	InterDigital
R2-2107307	L2 U2N relaying Adaptation layer design aspects	Intel Corporation
R2-2107356	Remaining issues on adaptation layer for L2 relay	Spreadtrum Communications
R2-2107451	Adaptation Layer for L2 SL Relay	vivo
R2-2107470	UP aspects on Layer 2 SL relay	Ericsson
R2-2107620	Discussion on adaptation header in PC5 link	Apple
R2-2107734	Remaining Issues in Adaptation Layer Design	Futurewei
R2-2108148	Discussion on adaptation layer design	ZTE, Sanechips
R2-2108250	Sidelink Relay Uu RLC for Remote UE and Adaptation Layer Design	Beijing Xiaomi Mobile Software
R2-2108466	Discussion on Uu adaptation layer in L2 UE-to-NW relay	Nokia, Nokia Shanghai Bell
R2-2108484	Summary for Relay Adaptation Layer - AI 8.7.2.3	InterDigital France R&D, SAS
R2-2108511	Adaption layer for L2 U2N relay	CMCC
R2-2108623	Adaptation layer functionalities for L2 U2N relay	Huawei, HiSilicon
R2-2108934	[R2 AT115-e][604][Relay] Discussion on Adaptation Layer	OPPO
R2-2108947	[R2 AT115-e][604][Relay] Discussion on Adaptation Layer	OPPO
8.7.2.4	QoS
R2-2106993	End-to-end QoS Management for L2 Sidelink Relay	CATT
R2-2107040	Discussion on resource allocation and QoS management for L2 U2N relay	OPPO
R2-2107107	Discussion on E2E QoS enforcement in L2 U2N relay	Qualcomm Incorporated
R2-2107278	Discussion on QoS for L2 UE to NW Relays	InterDigital
R2-2107308	E2E QoS management considerations for L2 U2N relaying	Intel Corporation
R2-2107471	Aspects for QoS management with SL relay	Ericsson
R2-2107497	E2E QoS Provisioning with L2 Sidelink Relay	Fraunhofer IIS, Fraunhofer HHI
R2-2107624	QoS enhancements for UE-to-NW relay	Apple
R2-2107712	QoS management aspects for L2 U2N Relay	Samsung
R2-2107758	Mechanisms for E2E QoS management	vivo
R2-2107833	Considerations on voice and video support for Relays	Philips International B.V., MediaTek, Vivo, FirstNet
R2-2108149	Discussion on QoS of SL relay	ZTE, Sanechips
R2-2108512	Mechanisms for E2E QoS management	CMCC
R2-2108624	QoS management of L2 U2N relay	Huawei, HiSilicon
R2-2108821	On recommended bit rate	MediaTek Inc.
R2-2109018	[Pre115-e][605][Relay] Summary of AI 8.7.2.4 QoS (Apple)	Apple
8.7.3.1	Relay discovery
R2-2106994	Leftover Issues for Sidelink Discovery	CATT
R2-2107089	Remaining issues on relay discovery	Qualcomm Incorporated
R2-2107212	Discussion on remaining issue of relay discovery	OPPO
R2-2107279	Remaining Issues on Discovery	InterDigital
R2-2107313	Leftover aspects of Relay discovery	Intel Corporation
R2-2107468	Left issues for SL discovery	Ericsson
R2-2107713	Resource allocation for SL relay discovery message	Samsung
R2-2107759	Remaining issues on Relay Discovery	vivo
R2-2107889	Relay Discovery for L2 and L3 relay	Lenovo, Motorola Mobility
R2-2107950	Further issues on the discovery message for NR sidelink relay	Nokia, Nokia Shanghai Bell
R2-2108143	Further discussion on Relay discovery	ZTE, Sanechips
R2-2108152	Relay Discovery transmission for stage 3	LG Electronics Inc.
R2-2108251	Relay Discovery Resource Pool Utilisation	Beijing Xiaomi Mobile Software
R2-2108324	Coexistence of discovery resource pools	Kyocera
R2-2108626	Remaining issue on relay discovery	Huawei, HiSilicon
R2-2108949	[AT115-e][617][Relay] Continuation of discussion on discovery (CATT)	CATT
8.7.3.2	Relay re/selection
R2-2106995	New Triggers for Relay Reselection	CATT
R2-2107102	Remaining issues on relay (re)selection	Qualcomm Incorporated
R2-2107305	Leftover aspects of Relay reselection	Intel Corporation
R2-2107469	Aspects for SL relay selection and reselection	Ericsson
R2-2107760	Remaining issues on Relay (re)selection	vivo
R2-2107872	Discussion on sidelink relay reselection	SHARP Corporation
R2-2107890	Relay (re)selection for L2 and L3 relay	Lenovo, Motorola Mobility
R2-2108144	Further discussion on Relay selection	ZTE, Sanechips
R2-2108252	Use of Cell ID in Sidelink L2 Relay (Re)selection	Beijing Xiaomi Mobile Software
R2-2108467	Discussion on sidelink assisted mobility using UE-to-Nwk Relay	Nokia, Nokia Shanghai Bell
R2-2108625	Discussion on relay reselection	Huawei, HiSilicon
R2-2108706	Remaining issues for L2 U2N relay (re)selection	MediaTek Inc.
8.8.1	Organizational
R2-2106972	LS on Cell reselection with band-specific network slices (S2-2105158; contact: Nokia)	SA2
8.8.2	Cell reselection
R2-2107108	Further discussion on slice specific cell reselection	Qualcomm Incorporated
R2-2107243	Considerations on slice based cell reselection	Beijing Xiaomi Software Tech
R2-2107372	Discussion on slice based cell reselection	Spreadtrum Communications
R2-2107383	Discussion on Slice based Cell Reselection	CATT
R2-2107443	Functional aspects of slice specific cell reselection	Intel Corporation
R2-2107461	Discussion on slice based cell reselection	China Telecommunication, Baicells
R2-2107466	Cell reselection in RAN slicing	FGI, Asia Pacific Telecom
R2-2107505	Considerations on contents of slice related cell selection info	KDDI Corporation
R2-2107592	Slice based cell reselection under NW control	Apple
R2-2107705	Discussion on slice based cell reselection	LG Electronics UK
R2-2107730	Discussion on slice aware cell reselection	ZTE corporation, Sanechips
R2-2107739	Consideration on slice-specific cell reselection	OPPO
R2-2107929	Discussion on slice-based cell reselection prioritization	BT plc
R2-2107951	Reply proposal for LS on cell reselection with band-specific network slices (S2-2105158/ R2-2106972)	Nokia, Nokia Shanghai Bell
R2-2107952	Proposals for slice specific cell reselection solutions	Nokia, Nokia Shanghai Bell
R2-2108025	Summary of [Post114-e][251][Slicing] Solution direction	Lenovo, Motorola Mobility (Rapporteur)
R2-2108292	Slice grouping	Ericsson
R2-2108315	Considerations on slice-based cell reselection	Lenovo, Motorola Mobility
R2-2108316	On slice priority for cell reselection	Samsung R&D Institute UK
R2-2108433	Slice information provided by RRCRelease	SHARP Corporation
R2-2108497	Discussion on the solutions for slice based cell reselection	CMCC
R2-2108554	Discussion on slice based cell reselection under network control	Huawei, HiSilicon
R2-2108842	Resolving FFSs for Option 4	Lenovo, Motorola Mobility
R2-2108859	Summary of [AT115-e][240][Slicing] Reply LS to SA2 on band-specific slices in cell reselection (NN)	NN
R2-2108860	[Draft] Reply LS on Cell reselection with band-specific network slices	Nokia
R2-2108868	Reply LS on Cell reselection with band-specific network slices	RAN2
R2-2108928	LS on Slice list and priority information for cell reselection	RAN2
8.8.3	RACH
R2-2107109	Further discussion on slice specific RACH	Qualcomm Incorporated
R2-2107241	Considerations on slice based RACH configuration	Beijing Xiaomi Software Tech
R2-2107384	Analysis on slice based RACH configuration	CATT
R2-2107444	Further considerations of slice based RACH	Intel Corporation
R2-2107506	Slice-specific RACH configurations	Nokia, Nokia Shanghai Bell
R2-2107593	Slice based RACH configuration	Apple
R2-2107714	Slice specific RACH type selection	Samsung
R2-2107731	Slice specific RACH resources and RACH prioritization	ZTE corporation, Sanechips
R2-2107740	Consideration on slice-specific RACH	OPPO
R2-2108293	RACH for RAN slicing enhancement	Ericsson
R2-2108498	Open issues for slice based RACH configuration	CMCC
R2-2108504	Report for [Post114-e][252][Slicing] RACH partitioning details for slicing	CMCC
R2-2108555	Discussion on slice based RACH configuration	Huawei, HiSilicon
R2-2108759	Further discussion on slice-specific RACH	LG electronics Inc.
R2-2108839	Report for [Post114-e][252][Slicing] RACH partitioning details for slicing	CMCC
8.9.1	Organizational
R2-2108917	LS on UE Power Saving	RAN2
R2-2108927	Introduction of Rel-17 UE power saving enhancements	Huawei, HiSilicon
8.9.2	Idle/inactive-mode UE power saving
R2-2107258	Discussion on CN-assigned paging grouping	Transsion Holdings
R2-2108062	Discussion on enhancements for idle/inactive-mode UE power saving	Sony
R2-2108685	Summary of [Post114-e][076][ePowSav] Paging SubGrouping	CATT
8.9.2.1	Architecture
R2-2106998	Further details of UE Subgrouping	Samsung Electronics Co., Ltd
R2-2107067	Discussion on grouping-based paging	OPPO
R2-2107068	Discussion on UE paging capabilities	OPPO
R2-2107222	Paging subgroup assignment	Qualcomm Incorporated
R2-2107385	The architecture of paging enhancement	Xiaomi Communications
R2-2107406	Architecture for paging enhancement by UE subgrouping	vivo
R2-2107549	Further considerations on Network assigned subgrouping	Intel Corporation
R2-2107721	Further discussion on CN-assigned paging grouping	Transsion Holdings
R2-2107880	UE ID based subgroup	LG Electronics Inc.
R2-2107902	Consideration on Idle/inactive-mode UE power saving	Lenovo, Motorola Mobility
R2-2108011	CN and RAN responsibility split for paging subgrouping	Nokia, Nokia Shanghai Bell
R2-2108027	Further discussion on paging subgrouping	Huawei, HiSilicon
R2-2108028	Discussion on paging subgrouping supporting on UE and network	Huawei, HiSilicon
R2-2108237	Grouping methods for Paging	Ericsson
R2-2108461	Handling network nodes not supporting UE paging subgrouping	Futurewei Technologies
R2-2108590	UE Paging Subgroup Assignment	MediaTek Inc.
R2-2108592	CN and RAN responsibility split for paging subgrouping	Nokia, Nokia Shanghai Bell
R2-2108686	Further Consideration on Paging Subgroup	CATT
R2-2109094	[AT115-e][043][ePowSav] Paging Subgrouping (Nokia)	Nokia (Rapporteur)
8.9.2.2	Control and Procedure details
R2-2106999	UE Idenity for paging subgrouping	Samsung Electronics Co., Ltd
R2-2107000	DRX cycle for monitoring paging	Samsung Electronics Co., Ltd
R2-2107069	Discussion on PEI monitoring	OPPO
R2-2107223	Paging reception with cross-slot scheduling	Qualcomm Incorporated
R2-2107407	UE subgrouping procedure for paging enhancement	vivo
R2-2107538	How a UE determines the PEI radio resource(s) to monitor for paging	Xiaomi Communications
R2-2107553	Further considerations on the UE behaviour for Network assigned subgrouping	Intel Corporation
R2-2107595	Signallaing aspects of IDLE/INACTIVE paging subgrouping for enhanced power save	Apple
R2-2107879	NW assigned subgroup	LG Electronics Inc.
R2-2107881	Paging subgroup indication	LG Electronics Inc.
R2-2107903	Consideration on the configuration for UE paging grouping	Lenovo, Motorola Mobility
R2-2108012	Subgroup indication via PEI	Nokia, Nokia Shanghai Bell
R2-2108029	Further considerations on other paging enhancements	Huawei, HiSilicon
R2-2108238	PEI monitoring in NR: CN and System level impacts	Ericsson
R2-2108272	Further Consideration on NW assigned subgrouping and UE ID based grouping	ZTE Corporation
R2-2108534	Considerations on assistance information and procedures for paging subgrouping	CMCC
R2-2108593	Paging Monitoring with PEI and UE Subgrouping	MediaTek Inc.
8.9.3	Other aspects RAN2 impacts
R2-2107001	TRS_CSIRS for RRC IDLE and RRC INACTIVE	Samsung Electronics Co., Ltd
R2-2107070	Discussion on signaling aspects of TRS/CSI-RS occasion(s) for idle/inactive Ues	OPPO
R2-2107408	Discussion on TRS CSI-RS in idle inactive mode	vivo
R2-2107409	RAN2 impact on RLM/BFD relaxation for power saving	vivo
R2-2107536	Discussion on TRS CSI-RS for RRC-IDLE and RRC-INACTIVE State UE	Xiaomi Communications
R2-2107537	LS to RAN1 on TRS CSI-RS for RRC-IDLE and RRC-INACTIVE State UE	Xiaomi Communications
R2-2107550	TRS/CSI-RS configuration and availability for idle/inactive-mode UE	Intel Corporation
R2-2107596	TRS/CSI-RS signalling aspects for IDLE/INACTIVE UEs for enhanced power save	Apple
R2-2107901	TRS/CSI-RS configuration for Idle/inactive mode UE	Lenovo, Motorola Mobility
R2-2108013	RAN2 impact on connected mode power saving	Nokia, Nokia Shanghai Bell
R2-2108030	Discussion on potential TRS/CSI-RS	Huawei, HiSilicon
R2-2108063	Discussion on TRS/CSI-RS configuration of idle/inactive-mode UEs	Sony
R2-2108239	Provision of TRS Configurations to UEs in idle and inactive	Ericsson
R2-2108240	TRS Availability Signaling to UEs in idle and inactive	Ericsson
R2-2108263	Potential TRS/CSI-RS occasion(s)	Nokia, Nokia Shanghai Bell
R2-2108271	Further Consideration On TRS and CSI-RS for idle and inactive UE	ZTE Corporation
R2-2108535	Considerations on TRS/CSI-RS occasion(s) for idle/inactive UE(s)	CMCC
R2-2108687	Further Consideration on Configuration of TRS/CRI-RS	CATT
R2-2109037	Summary of 8.9.3 - Other aspects RAN2 impacts	Ericsson
R2-2109072	Report from [AT115-e][044][ePowSav] TRS CSIRS for RRC Idle and Inactive (Ericsson)	Ericsson
8.10.1	Organizational
R2-2106904	LS reply on multiple TACs per PLMN (C1-213965; contact: Nokia)	CT1
R2-2106922	Reply LS on PDB for new 5QI (R1-2106331; contact: Ericsson)	RAN1
R2-2106924	Reply LS on TA pre-compensation (R1-2106341; contact: OPPO)	RAN1
R2-2106940	Reply LS on SA WG2 assumptions from conclusion of study on architecture aspects for using satellite access in 5G (R3-212916; contact: Ericsson)	RAN3
R2-2106941	Reply LS on UE location aspects in NTN (R3-212917; contact: Qualcomm)	RAN3
R2-2106966	LS Response to LS on multiple TACs per PLMN (S2-2104891; contact: Qualcomm)	SA2
R2-2106976	Reply LS on UE location aspects in NTN (S3-212306; contact: Huawei)	SA3
R2-2107146	Updated NR-NTN-solutions work plan	THALES
R2-2107346	Draft Reply LS on UE location aspects in NTN	Huawei, HiSilicon
R2-2107523	Draft Response LS on Multiple TACs per PLMN	Nokia, Nokia Shanghai Bell
R2-2107568	[Draft] Reply LS on UE location aspects in NTN	Qualcomm Incorporated
R2-2107732	Stage-3 running 304 CR for NTN	ZTE corporation, Sanechips
R2-2108345	Stage-3 running RRC CR for NTN Rel-17	Ericsson
R2-2108664	Stage 3 NTN running CR for 38.321 - RAN2#115	InterDigital
R2-2108829	Stg 2 Running CR_38.300_NR-NTN	THALES
R2-2108875	Report of [Post115-e][102][NTN] Reply LS on UE location aspects (Huawei)	Huawei, HiSilicon
R2-2108885	[Draft] Reply LS on UE location aspects in NTN	Qualcomm Incorporated
R2-2108886	Draft Reply LS on UE location aspects in NTN	Huawei
R2-2108888	Response LS on Multiple TACs per PLMN	RAN2
R2-2109128	[Draft] Reply LS on UE location aspects in NTN	Qualcomm Incorporated
R2-2109216	Reply LS on UE location aspects in NTN	RAN2
R2-2109217	Reply LS on UE location aspects in NTN	RAN2
8.10.2	User Plane
R2-2107280	User Plane Issues and Enhancements for an NTN	Samsung Research America
R2-2108663	MAC open issues in NTN - RAN2#115	InterDigital
8.10.2.1	RACH aspects
R2-2107075	Discussion on RACH in NTN	OPPO
R2-2107314	Discussion on UE Specific TA Report	CATT
R2-2107362	TA report in Random access procedure	Spreadtrum Communications
R2-2107908	Considerations on new criteria for RA type selection	Lenovo, Motorola Mobility
R2-2107972	RACH Type selection and TA report	Beijing Xiaomi Mobile Software
R2-2108114	Further discussion on RACH issues for NR NTN	Nokia, Nokia Shanghai Bell
R2-2108350	Considerations on RACH aspects	ZTE Corporation, Sanechips
R2-2108453	Random Access timers and reporting information about UE specific TA pre-compensation in NTNs	Ericsson
R2-2108609	Discussion on RACH and TA report aspects	LG Electronics Inc.
R2-2108715	Discussion on LCH-based RA type selection	ASUSTeK
R2-2108882	Report of [AT115-e][106][NTN] RACH aspects (CATT)	CATT
R2-2108897	Report of [AT115-e][106][NTN] RACH aspects (CATT)	CATT
R2-2108901	Report of [AT115-e][106][NTN] RACH aspects (CATT)	CATT
8.10.2.2	Other MAC aspects
R2-2107076	Discussion on UL HARQ retransmission in NTN	OPPO
R2-2107315	Discussion on HARQ Aspects and UL Scheduling Enhancement in NTN	CATT
R2-2107361	Discussion on HARQ and LCP remaining issues	Spreadtrum Communications
R2-2107449	Impact on DRX timers with UL/DL HARQ enhancement in NTN	vivo
R2-2107450	Impact on LCP with disabled UL HARQ retransmission in NTN	vivo
R2-2107563	LCP restriction for an UL HARQ process	Qualcomm Incorporated, Huawei, HiSilicon, Xiaomi, Samsung
R2-2107632	HARQ Management and LCP Restrictions in NTN	Apple
R2-2107790	Co-existence issue of BSR over CG and BSR over 2-step RACH	PANASONIC R&D Center Germany
R2-2107909	BSR with configured 2-step RACH and CG	Lenovo, Motorola Mobility
R2-2107986	Consideration on HARQ aspects	Beijing Xiaomi Mobile Software
R2-2108115	Discussion on remaining MAC issues for NR NTN	Nokia, Nokia Shanghai Bell
R2-2108318	On disabling uplink HARQ retransmission and associated LCP impacts	MediaTek Inc.
R2-2108319	Round trip delay offset for configured grant timer	MediaTek Inc.
R2-2108351	Considerations on HARQ aspects	ZTE Corporation, Sanechips
R2-2108452	On DRX, LCP, HARQ, SR/BSR, and configured scheduling	Ericsson
R2-2108544	Discussion on LCP Restrictions and CG Impact in NTN	CMCC
R2-2108608	Discussion on other MAC aspects	LG Electronics Inc.
R2-2108610	Consideration on LCP in NTN	Huawei, HiSilicon
R2-2108611	Discussion on TA report	Huawei, HiSilicon
R2-2108661	UL HARQ retransmission	InterDigital
R2-2108662	Impact of UE-gNB RTT determination on MAC	InterDigital
R2-2108716	Discussion on UL retransmission and DRX RTT timer	ASUSTeK
R2-2108768	HARQ Retransmission Enabling/Disabling for CG aspects	ITL
R2-2108883	Summary of [AT115-e][101][NTN] Other MAC aspects	InterDigital
R2-2108896	Summary of [AT115-e][101][NTN] Other MAC aspects: Phase 2	InterDigital (summary rapporteur)
R2-2109031	[Pre115-e][101][NTN] Summary of AI 8.10.2.2 - Other MAC aspects (InterDigital)	InterDigital
8.10.2.3	RLC and PDCP aspects
R2-2108317	RLC and PDCP timers extension	NEC Telecom MODUS Ltd.
R2-2108451	On RLC and PDCP for NTNs	Ericsson
R2-2108460	On RLC t-Reassembly for NTN	Sequans Communications
8.10.3.1	General aspects
R2-2107077	Discussion on UE location aspects in NTN	OPPO
R2-2107131	Signalling Solution for Feeder Link Switching of NTN	VODAFONE Group Plc
R2-2107150	Virtual cells for network verified UE position in NTN networks	Fraunhofer IIS; Fraunhofer HHI; Thales
R2-2107281	Remaining Beam Issues in an NTN: Tracking Area Management and Elliptical Beams	Samsung Research America
R2-2107284	Area Management in an NTN	Samsung Research America, Thales, Rakuten Mobile, and Apple
R2-2107316	Further Discussion on LCS and TAC aspects in NTN	CATT
R2-2107343	Discussion on V2X-like zone ID	Huawei, HiSilicon
R2-2107345	Draft Reply LS on multiple TACs per PLMN	Huawei, HiSilicon
R2-2107360	Discussion on TAC update in NTN	Spreadtrum Communications
R2-2107520	On Tracking Area Code handling for NTN	Nokia, Nokia Shanghai Bell
R2-2107564	Tracking area update timing	Qualcomm Incorporated
R2-2107567	Discussion on RAN3 LS reply on UE location	Qualcomm Incorporated
R2-2107633	NTN Area Management	Apple
R2-2107729	Discussion on the remaining issue on TAC update	vivo
R2-2108323	On Soft-switch based Tracking Area Updates in NR-NTN	MediaTek Inc.
R2-2108606	TAC update and UE location report	ZTE corporation, Sanechips
R2-2108848	[Pre115-e][102][NTN] Summary of AI 8.10.3.1 - LCS aspects only	Qualcomm Inc.
R2-2108884	[offline 102] LCS aspects	Qualcomm
R2-2108887	[offline 107] Reply LS on TAC handling	Nokia
R2-2108898	[offline 102] LCS aspects - second round	Qualcomm Incorporated
R2-2108902	[Draft] LS on NTN specific user consent for obtaining UE location by gNB	Qualcomm
R2-2109199	LS on NTN specific user consent	RAN2
8.10.3.2	Idle/Inactive mode
R2-2107078	Discussion on idle/inactive mode procedures in NTN	OPPO
R2-2107282	Cell Reselection, System Information, Paging Enhancements, and Power-Efficient Neighbor Cell Search for an NTN	Samsung Research America
R2-2107317	Further Discussion on the Leftover Issues of IDLE/INACTIVE	CATT
R2-2107344	Discussion on cell reselection	Huawei, HiSilicon
R2-2107359	Discussion on stop serving time of NTN cell	Spreadtrum Communications
R2-2107448	Remaining issues on cell reselection for NTN	vivo
R2-2107630	On NTN Ephemeris Definitions and Signaling	Apple
R2-2107634	Cell Selection and Cell Reselection Solutions for Non Terrestrial Networks	Apple
R2-2107733	Further consideration on cell selection and reselection in NTN	ZTE corporation, Sanechips
R2-2107845	Remaining issues in NTN Idle mode	LG Electronics Inc.
R2-2107853	Issues of cell reselection for prioritizing TN over NTN	ITRI
R2-2107910	Considerations on ephemeris provision for NTN	Lenovo, Motorola Mobility
R2-2108064	Idle mode enhancement in NTN	Sony
R2-2108170	Cell selection and reselection enhancements for NTN	Xiaomi
R2-2108234	NTN to TN mobility in Idle/Inactive mode	NEC Telecom MODUS Ltd.
R2-2108235	NTN Neighbour Cell information	NEC Telecom MODUS Ltd.
R2-2108281	Idle mode aspects for NTN	Ericsson
R2-2108320	On Cell Re-selection in NR-NTN	MediaTek Inc.
R2-2108412	NTN type and scenario indication	Convida Wireless
R2-2108413	NTN Cell (re)selection enhancements	Convida Wireless
R2-2108526	Discussion on location assisted cell reselection	CMCC, Huawei, HiSilicon
R2-2108779	NTN Idle/Inactive mode cell re-selection	ITL
R2-2108889	Report of [AT115-e][108][NTN] idle mode aspects (ZTE)	ZTE corporation, Sanechips
R2-2108899	Report of [AT115-e][108][NTN] idle mode aspects (ZTE) – Second Round	ZTE corporation, Sanechips
R2-2108903	Report of [AT115-e][108][NTN] idle mode aspects (ZTE) – Third Round	ZTE corporation, Sanechips
8.10.3.3	Connected mode
R2-2107079	Discussion on mobility management for connected mode UE in NTN	OPPO
R2-2107283	Remaining Issues on Handover and Neighbor Search for an NTN	Samsung Research America
R2-2107318	Discussion on NTN CP left issues	CATT
R2-2107447	Discussion on CHO related aspects for NTN	vivo
R2-2107457	Consideration of location reporting in NTN CHO	China Telecommunication
R2-2107519	Further discussion on CHO in NTN	Rakuten Mobile, Inc
R2-2107521	Further views on SMTC configurations for NTN	Nokia, Nokia Shanghai Bell
R2-2107522	Even further thoughts on mobility in NTN	Nokia, Nokia Shanghai Bell
R2-2107565	Open issues in CHO	Qualcomm Incorporated
R2-2107566	SMTC and MG enhancements	Qualcomm Incorporated
R2-2107631	On NTN Conditional Handovers	Apple
R2-2107704	Discussion on NTN-TN service continuity	KT Corp.
R2-2107846	Remaining issues for NTN connected mode mobility	LG Electronics Inc.
R2-2107878	Measurement window enhancements for NTN cell	LG Electronics Inc.
R2-2107911	UE assistance for measurement gap and SMTC configuration in NTN	Lenovo, Motorola Mobility
R2-2107912	Execution condition for CHO in NTN	Lenovo, Motorola Mobility
R2-2107987	Consideration on RRC release	Beijing Xiaomi Mobile Software
R2-2108017	Discussion on connected mode aspects for NTN	Xiaomi Communications
R2-2108065	Signaling storm during HOs and Timer based trigger details	Sony
R2-2108066	Cell coverage spillage over multiple countries issue in NTN	Sony
R2-2108067	SMTC enhancement in NTN	Sony
R2-2108100	Service continuity between NTN and TN	Turkcell, Hughes/EchoStar, Network Systems, Thales, BT Plc, Vodafone, ESA, Inmarsat, Aselsan
R2-2108198	Discussion on UE feedback based SMTC and GAPS measurement configuration	Rakuten Mobile, Inc
R2-2108286	Remaining Issues on SMTC and measurement Gap configuration for NTN	CMCC,Ericsson,ZTE Corporation,Huawei,CATT,Lenovo, Motorola Mobility
R2-2108326	Efficient Configuration of SMTC and Measurement Gaps in NR-NTN	MediaTek Inc.
R2-2108329	Mobility for NTN-TN scenarios	MediaTek Inc.
R2-2108341	Connected mode aspects for NTN	Ericsson
R2-2108527	Signaling overhead reduction for connected mobility	CMCC
R2-2108528	Discussion on NTN-TN mobility	CMCC
R2-2108607	Further consideration on CHO in NTN	ZTE corporation, Sanechips
R2-2108717	Discussion on location-based measurement event triggering	ASUSTeK
R2-2108890	[AT115-e][103][NTN] CHO and NTN -TN mobility aspects (Ericsson)	Ericsson
R2-2108900	[AT115-e][103][NTN] CHO and NTN -TN mobility aspects (Ericsson)	Ericsson
R2-2108904	[AT115-e][103][NTN] CHO and NTN -TN mobility aspects (Ericsson)	Ericsson
R2-2109025	[Pre115-e][103][NTN] Summary of AI 8.10.3.3 - CHO and NTN -TN mobility aspects only (Ericsson)	Ericsson
R2-2109056	[AT115-e][103][NTN] CHO and NTN -TN mobility aspects (Ericsson)	Ericsson
R2-2109135	Report of [AT115-e][112][NTN] SMTC and gaps (CMCC)	CMCC
R2-2109136	[AT115-e][103][NTN] CHO and NTN -TN mobility aspects (Ericsson)	Ericsson
R2-2109219	LS to RAN4 on SMTC	RAN2
8.11.1	Organizational
R2-2106913	LS on support of UL-AOA/ZOA assistance information signalling for NR positioning (R1-2106202; contact: Intel)	RAN1
R2-2106918	Reply LS to SA2 on Scheduling Location in Advance (R1-2106312; contact: Qualcomm)	RAN1
R2-2106919	LS on granularity of response time (R1-2106316; contact: Huawei)	RAN1
R2-2106920	LS on Positioning Reference Units (PRUs) for enhancing positioning performance (R1-2106326; contact: CATT)	RAN1
R2-2106968	Response LS on Scheduling Location in Advance to reduce Latency (S2-2105122; contact: CATT)	SA2
R2-2106969	LS on determination of location estimates in local co-ordinates (S2-2105124; contact: Ericsson)	SA2
R2-2106971	LS on storage of UE Positioning Capabilities (S2-2105153; contact: Qualcomm)	SA2
R2-2107133	Draft Response LS to SA2 on the scheduled location time	CATT
R2-2107144	Draft Response LS to RAN1 on the Positioning Reference Units (PRUs) for positioning enhancement	CATT
R2-2107674	Consideration on stage 2 structure on RAT dependent positioning	Intel Corporation
R2-2108401	Local Co-ordinates support for Positioning methods	Ericsson
R2-2108402	[Draft] Reply LS on determination of location estimates in local co-ordinates	Ericsson
R2-2108940	[AT115-e][610][POS] PRUs (CATT)	CATT
R2-2108941	[Draft] LS to SA2 on network management of UE-typed PRUs	CATT
R2-2108942	[Draft] Reply LS on determination of location estimates in local co-ordinates	Ericsson
R2-2108957	Reply LS on determination of location estimates in local co-ordinates	RAN2
8.11.2	Latency enhancements
R2-2107090	Discussion on positioning latency reduction	ZTE
R2-2107091	Discussion on scheduled location time	ZTE
R2-2107132	Discussion on Response LS on Scheduling Location in Advance to reduce Latency from SA2	CATT
R2-2107134	Discussion on Enhancements for Latency Reduction	CATT
R2-2107135	Discussion on storage of UE Positioning Capabilities LS from SA2 and the granularity of response time LS from RAN1	CATT
R2-2107399	Further consideration of positioning latency enhancements	OPPO
R2-2107500	Discussion on positioning latency	Huawei, HiSilicon
R2-2107641	Discussion on latency enhancement	vivo
R2-2107642	Discussion on Scheduling Location in Advance to reduce Latency	vivo
R2-2107670	Scheduled location time based latency reduction	Intel Corporation
R2-2107673	Storing UE positioning capability in AMF	Intel Corporation
R2-2107680	Summary of agenda 8.11.2 Latency enhancements	Intel Corporation
R2-2107681	Discussion on Enhancements for Latency Reduction	InterDigital, Inc.
R2-2107962	Discussion on the response time	Samsung
R2-2108127	Positioning Latency Reduction Enhancements	Lenovo, Motorola Mobility
R2-2108175	Positioning enhancements on latency reduction	Xiaomi
R2-2108367	Scheduling Location in Advance to Reduce Latency	Qualcomm Incorporated
R2-2108376	[draft] Response LS on Scheduling Location in Advance to reduce Latency	Qualcomm Incorporated
R2-2108377	LPP impacts for UE positioning capability storage	Qualcomm Incorporated
R2-2108378	[draft] Response LS on storage of UE Positioning Capabilities	Qualcomm Incorporated
R2-2108393	Utilizing Time T and other associated parameters	Ericsson
R2-2108397	On UE Positioning Capabilities	Ericsson
R2-2108536	Discussion on latency reduction for positioning	CMCC
R2-2108704	Enhancement to reduce latency for high volume positioning	Nokia, Nokia Shanghai Bell
R2-2108769	Handling of multiple QoS for latency reduction	Samsung Electronics
R2-2108771	Latency reduction via configured grant for positioning	Samsung Electronics
R2-2108773	Discussion on the scheduled location time	Samsung Electronics
R2-2108943	Draft Reply LS to SA2 on scheduled location time	CATT
R2-2108944	Draft reply LS on granularity of response time	Huawei, HiSilicon
R2-2108945	[draft] Response LS on storage of UE Positioning Capabilities	Qualcomm
R2-2108958	Reply LS to SA2 on scheduled location time	RAN2
R2-2108959	Reply LS on granularity of response time	RAN2
R2-2108960	Response LS on storage of UE Positioning Capabilities	RAN2
R2-2109102	Summary of [AT115-e][614][POS] Reply LS to SA2 on capability storage (Qualcomm)	Qualcomm Incorporated
R2-2109126	[AT115-e][612][POS] Reply LS to SA2 on scheduled location time (CATT)	CATT
R2-2109227	LS on UE ID in adaptation layer	RAN2
8.11.3	RRC_INACTIVE
R2-2107092	Discussion on positioning in RRC INACTIVE state	ZTE
R2-2107093	Stage 2 procedures for positioning in RRC INACTIVE state	ZTE
R2-2107142	Discussion on Positioning for UEs in RRC_INACTIVE state	CATT
R2-2107149	Considerations on positioning in RRC_INACTIVE mode	Fraunhofer IIS; Fraunhofer HHI
R2-2107358	Discussion on positioning in RRC_INACTIVE state	Spreadtrum Communications
R2-2107502	[DRAFT] LS on positioning for the UE in RRC_INACTIVE	Huawei, HiSilicon
R2-2107639	Positioning procedures in RRC_INACTIVE (stage-2)	Apple
R2-2107643	Enhancement of DL positioning in RRC_INACTIVE	vivo
R2-2107644	Configuration of UL positioning in RRC_INACTIVE	vivo
R2-2107671	Support of Positioning in RRC_INACTIVE	Intel Corporation
R2-2107683	Discussion on Positioning in RRC INACTIVE state	InterDigital, Inc.
R2-2107684	Discussion on reporting of Positioning Information with SDT	InterDigital, Inc.
R2-2107829	Supporting positioning in RRC_INACTIVE state	OPPO
R2-2107830	Discussion on UL Positioning methods in RRC_INACTIVE state	OPPO
R2-2108068	Considerations on positioning RRC Inactive	Sony
R2-2108128	On Positioning in RRC_INACTIVE state	Lenovo, Motorola Mobility
R2-2108173	Discussion on positioning for UEs in RRC Inactive	Xiaomi
R2-2108383	Summary of [Post114-e][602][POS] Stage 2 procedure for deferred MT-LR in RRC_INACTIVE	Qualcomm Incorporated
R2-2108394	Inactive mode Positioning	Ericsson
R2-2108605	Way-forward for RRC_INACTIVE positioning	Huawei, China Unicom, China Telecom, Futurewei, HiSilicon, Intel Corporation, Interdigital, Spreadtrum Communications, VIVO, Xiaomi, ZTE Corporation
R2-2108703	Considerations on positioning in RRC_INACTIVE	Nokia, Nokia Shanghai Bell
R2-2108764	Considerations on Positioning in RRC_INACTIVE state	CMCC
R2-2108772	On message segmentation for transmitting in Inactive state	Samsung Electronics
R2-2108826	Summary of AI 8.11.3 for RRC_INACTIVE positioning	ZTE
R2-2108946	[AT115-e][615][POS] UL and UL DL positioning in RRC_INACTIVE (Huawei)]	Huawei, HiSilicon
8.11.4	On-demand PRS
R2-2107094	Discussion on on-demand PRS	ZTE
R2-2107148	On-demand PRS	Fraunhofer IIS, Fraunhofer HHI
R2-2107498	Discussion on on-demand PRS	Huawei, HiSilicon
R2-2107638	Remaining issues of On-Demand PRS	Apple
R2-2107645	Discussion on on-demand PRS	vivo
R2-2107672	Support of on-demand PRS request	Intel Corporation
R2-2107686	Discussion on procedures for On-demand PRS for DL-based positioning	InterDigital, Inc.
R2-2107687	Discussion on procedure for On-demand PRS for DL+UL based positioning	InterDigital, Inc.
R2-2107828	Discussion on on-demand DL-PRS	OPPO
R2-2108069	Considerations on positioning PRS On-demand	Sony
R2-2108129	Support of On-Demand DL-PRS	Lenovo, Motorola Mobility
R2-2108174	Positioning enhancement to on-demand DL PRS	Xiaomi
R2-2108384	On-Demand DL-PRS	Qualcomm Incorporated
R2-2108395	On demand PRS	Ericsson
R2-2108400	Report on [Post114-e][603][POS] Procedures and signalling for on-demand PRS (Ericsson)	Ericsson
R2-2108705	NR E-CID for UE feedback for on-demand PRS	Nokia, Nokia Shanghai Bell
R2-2108774	Multiple QoS class using on-demand PRS	Samsung Electronics
R2-2108827	Summary of Agenda Item 8.11.4 On-demand PRS	CATT
R2-2108950	Draft Reply LS to RAN1 on on-demand DL PRS parameters	Intel
R2-2109061	LS to RAN2 with update on RAN1 discussion for on-demand DL PRS (R1-2108383; contact: Intel)	RAN1
R2-2109123	Reply LS to RAN1 on on-demand DL PRS parameters	RAN2
8.11.5	GNSS positioning integrity
R2-2107095	Discussion on positioning integrity	ZTE
R2-2107136	Discussion on Integrity KPIs impact and draft LS	CATT
R2-2107147	UE-aided detection of threat to GNSS systems and assistance data signaling	Fraunhofer IIS; Fraunhofer HHI; Ericsson
R2-2107398	Discussion on supporting positioing integrity in RAN	OPPO
R2-2107499	Discussion on positioning integrity	Huawei, HiSilicon
R2-2107503	Text Proposal for GNSS integrity	Huawei, HiSilicon
R2-2107646	Discussion on signalling and procedures for GNSS positioning integrity	vivo
R2-2107688	Discussion on procedures and signalling for GNSS positioning integrity	InterDigital, Inc.
R2-2107989	Email Summary [Post114-e][601][POS] GNSS integrity assistance information, KPIs, and reporting of integrity results (Swift)	Swift Navigation
R2-2108024	Positioning Integrity Support in LPP	Nokia, Nokia Shanghai Bell
R2-2108176	Discussion on GNSS positioning integrity	Xiaomi
R2-2108340	Bounding GNSS errors for positioning integrity	ESA, Nokia, Nokia Shanghai Bell
R2-2108385	Considerations on GNSS positioning integrity support	Qualcomm Incorporated
R2-2108396	GNSS positioning integrity	Ericsson
R2-2108474	Discussion on GNSS Integrity Assistance Data	Swift Navigation, Ericsson, Mitsubishi Electric Corporation
R2-2108475	Text Proposal on GNSS Integrity Assistance Data	Swift Navigation, Ericsson, Mitsubishi Electric Corporation
R2-2108770	Consideration on the signalling design for Positioning Integrity	Samsung Electronics
R2-2109029	Summary on agenda item 8.11.5 on GNSS positioning integrity	Qualcomm Incorporated
8.11.6	A-GNSS enhancements
R2-2107137	Summary of Introduction of B3I signal in BDS system	CATT, CAICT
R2-2107138	Introduction of B2a and B3I signal in BDS system in A-GNSS	CATT, CAICT
R2-2107139	Introduction of B2a and B3I signal in BDS system in A-GNSS	CATT, CAICT
R2-2107140	Introduction of B2a signal in BDS system in A-GNSS	CATT, CAICT
R2-2107141	Introduction of B3I signal in BDS system in A-GNSS	CATT, CAICT
R2-2107990	Text proposal on BDS ephemeris (B2I)	Swift Navigation
8.11.7	Other
R2-2107143	Discussion on Positioning Reference Units (PRUs) for positioning enhancement	CATT
R2-2107357	Discussion on PRU of positioning	Spreadtrum Communications
R2-2107501	Discussion on positioning enhancement	Huawei, HiSilicon
R2-2107647	Discussion on support for Positioning Reference Unit	vivo
R2-2107689	Discussion on supporting Positioning Reference Units	InterDigital, Inc.
R2-2107831	Discussion on the Positioning Reference Units (PRUs)	OPPO
R2-2108131	Support of Positioning Reference Units	Lenovo, Motorola Mobility
R2-2108386	Signalling and Procedures for supporting Positioning Reference Units	Qualcomm Incorporated
R2-2108398	On the Positioning Reference Units aspects	Ericsson
R2-2108399	On high accuracy aspects	Ericsson
8.12.1	Organizational
R2-2106905	Reply LS on introducing extended DRX for RedCap UEs (C1-213966; contact: Qualcomm)	CT1
R2-2106921	LS on RAN1 agreements on RAN2-led features for RedCap (R1-2106329; contact: NTT DOCOMO)	RAN1
R2-2106964	Reply LS on Unified Access Control (UAC) for RedCap (S1-211363; contact: Huawei)	SA1
R2-2108276	Revised WI work plan for RedCap	Ericsson
R2-2108277	Running 38331 CR for RedCap	Ericsson
R2-2108411	Running RedCap CR for 38.304	Ericsson
8.12.2.1	Definition of RedCap UE type and reduced capabilities
R2-2107208	Definition and reduced capabilities for RedCap UE	Huawei, HiSilicon
R2-2107351	Scaling factor for L2 buffer size reduction for Rel-17 RedCap	Spreadtrum Communications
R2-2107410	UE type defination and constraining for RedCap UEs	vivo, Guangdong Genius
R2-2107608	RRC Processing Delay and remaining RedCap UE capability aspects	Apple
R2-2107676	Email discussion report on [105][RedCap] Capabilities (Intel)	Intel Corporation
R2-2107677	Constraining network access for UE with reduced capabilities	Intel Corporation
R2-2107749	RedCap UE type and reduced capabilities	ZTE Corporation, Sanechips
R2-2108278	Definition of RedCap UE and discussion on capabilities	Ericsson
R2-2108697	Further discussions on Redcap UE capabilities	CATT
R2-2108891	Summary of [AT115-e][109][RedCap] Capabilities (Intel)	Intel Corporation
R2-2109103	WF on Rel-17 RedCap L2 soft buffer Reduction	Spreadtrum, Apple, CAICT, CEPRI, CMCC, CTC, CUC, GDCNI, Guangdong Genius, OPPO, Sequans, Xiaomi, u-blox AG, vivo
R2-2109129	Summary of [AT115-e][109][RedCap] Capabilities (Intel) - second round	Intel Corporation
R2-2109130	Draft Reply LS to RAN1 on L2 buffer size reduction	Intel, Spreadtrum
R2-2109198	LS to RAN1 on L2 buffer size reduction	RAN2
R2-2109218	LS on capability related RAN2 agreements for RedCap	RAN2
8.12.2.2	Identification, access and camping restrictions
R2-2107071	Discussion on RedCap UE’s early identification	OPPO
R2-2107072	Discussion on RedCap UE’s access restrictions	OPPO
R2-2107117	NR-REDCAP access restriction/allowance indication to ease mobility	THALES
R2-2107209	Identification and access restriction of RedCap UE	Huawei, HiSilicon
R2-2107216	Access and camping restriction for RedCap UEs	Qualcomm Incorporated
R2-2107352	Further discussion on early indication for RedCap UE	Spreadtrum Communications
R2-2107411	Identification and access restrictions for RedCap UEs	vivo, Guangdong Genius
R2-2107535	Discussion on Identification and UE access restrictions for Redcap devices	Xiaomi Communications
R2-2107555	Early identification and camping restrictions for RedCap UE	Sierra Wireless, S.A.
R2-2107606	Power-saving aspects from cell access and camping of RedCap UEs	Apple
R2-2107607	Issues with MSG3 based RedCap UE identification at intial access	Apple
R2-2107652	Camping restrictions of RedCap UE	Fujitsu
R2-2107678	Early identification and camping restrictions for RedCap UE	Intel Corporation
R2-2107707	Identification and access restrictions for RedCap UEs	LG Electronics UK
R2-2107750	Identification and Access Restriction for RedCap UEs	ZTE Corporation, Sanechips
R2-2107783	Access control for RedCap UEs	Samsung
R2-2107834	Camping restrictions and IFRI for RedCap UE	InterDigital, Europe, Ltd.
R2-2107870	Leftover issues on camping restriction and cell selection criterion	DENSO CORPORATION
R2-2108136	Further discussions on early identification and SI indication	NEC
R2-2108137	Initial BWP for RedCap	NEC
R2-2108244	Access for REDCAP UE	Nokia, Nokia Shanghai Bell
R2-2108245	REDCAP UE early identification	Nokia, Nokia Shanghai Bell
R2-2108279	Early indication & access restriction for RedCap UEs	Ericsson
R2-2108463	On Cell Barring Indication and Intra-Frequency Reselection Indication for RedCap UEs	Futurewei Technologies
R2-2108524	Discussion on identification and access restrictions	CMCC
R2-2108628	Access and camping restrictions for RedCap UE	China Telecommunications
R2-2108698	Early Identification and Camping Restrictions for Redcap UEs	CATT
R2-2108892	[AT115-e][104][RedCap] Identification, access and camping restrictions (Ericsson)	Ericsson (rapporteur)
R2-2109023	[Pre115-e][104][RedCap] Summary of AI 8.12.2.2 - Identification, access and camping restrictions (Ericsson)	Ericsson
R2-2109131	[AT115-e][104][RedCap] Identification, access and camping restrictions (Ericsson) - second round	Ericsson (rapporteur)
8.12.3.1	eDRX cycles
R2-2107073	Discussion on eDRX for RedCap UEs	OPPO
R2-2107096	CN PTW and RAN PTW for RedCap eDRX	Samsung
R2-2107210	eDRX for RedCap UE	Huawei, HiSilicon
R2-2107217	eDRX configurations for RedCap UEs	Qualcomm Incorporated
R2-2107412	Discussion on eDRX for RedCap UEs	vivo, Guangdong Genius
R2-2107534	Discussion on e-DRX for Redcap Devices	Xiaomi Communications
R2-2107675	Leftover issues for eDRX	Intel Corporation
R2-2107706	Discussion on eDRX for RRC_IDLE and RRC_INACTIVE	LG Electronics UK
R2-2107751	eDRX for RedCap UEs	ZTE Corporation, Sanechips
R2-2107905	Consideration on eDRX for RedCap UE	Lenovo, Motorola Mobility
R2-2108230	Remaining issues for eDRX	MediaTek Inc.
R2-2108280	Details of eDRX and PTW in RRC_IDLE and RRC_INACTIVE	Ericsson
R2-2108525	Discussion on eDRX for RRC_Idle and RRC_Inactive	CMCC
R2-2108699	Discussion on eDRX for NR RRC Inactive and Idle	CATT
R2-2108778	Open issues on eDRX for UE in RRC_INACTIVE	DENSO CORPORATION
R2-2108881	Summary of [AT115-e][105][REDCAP] eDRX cycles (vivo)	vivo
R2-2108893	Summary of offline 105 - [REDCAP] eDRX cycles - second round	vivo
R2-2109117	Summary of offline 105 - [REDCAP] eDRX cycles - second round	vivo
R2-2109132	Summary of offline 105 - [REDCAP] eDRX cycles - third round	vivo
R2-2109137	[Draft] LS to RAN4 on eDRX	vivo
R2-2109194	Summary of offline 105 - [REDCAP] eDRX cycles - third round	vivo
R2-2109196	LS to RAN4 on eDRX	RAN2
8.12.3.2	RRM relaxations
R2-2107074	Discussion on RRM relax for RedCap UEs	OPPO
R2-2107097	RedCap RRM relaxation in RRC_Idle/Inactive	Samsung
R2-2107098	RedCap RRM relaxation in RRC_Connected	Samsung
R2-2107110	RRM relaxation for Redcap UE	KDDI Corporation
R2-2107118	NR-REDCAP stationarity relaxations based on measurements	THALES
R2-2107145	On the efficient RRM relaxation on RRC connected mode	Fraunhofer IIS, Fraunhofer HHI
R2-2107211	RRM measurement relaxation for RedCap UE	Huawei, HiSilicon
R2-2107218	RRM relaxations for RedCap UEs	Qualcomm Incorporated
R2-2107386	Discussion on RRM measurement relaxation for redcap	Xiaomi Communications
R2-2107413	RRM relaxation for neighboring cell for RedCap UEs	vivo, Guangdong Genius
R2-2107679	RRM measurement relaxation criteria for RedCap devices	Intel Corporation
R2-2107748	RRM relaxation for RedCap UEs	ZTE Corporation, Sanechips
R2-2107754	RRM Relaxation for RedCap UE	NTT DOCOMO INC.
R2-2107847	Further considerations on RRM relaxation in RRC_IDLE and RRC_INACTIVE	LG Electronics Inc.
R2-2107848	Remaining issues in RRM relaxation in RRC_CONNECTED	LG Electronics Inc.
R2-2107873	RRM relaxation for RedCap UEs	SHARP Corporation
R2-2107904	RRM relaxation for stationary UE with reduced capability	Lenovo, Motorola Mobility
R2-2108070	Redcap relaxed measurements and number of beams	Sony
R2-2108071	RedCap Relaxed measurements, stationary definition	Sony
R2-2108259	On RRM relaxations for REDCAP	Nokia, Nokia Shanghai Bell
R2-2108260	On RRM relaxations in CONNECTED	Nokia, Nokia Shanghai Bell
R2-2108275	Details on RRM relaxation	Ericsson
R2-2108465	Discussion on Rel-17 not-at-cell-edge criterion	Futurewei Technologies
R2-2108518	Discussion on the RRM relaxation for RedCap Ues	CMCC
R2-2108629	RRM relaxation of RedCap UE	China Telecommunications
R2-2108700	Discussion on RRM relaxations for RRC_CONNECTED	CATT
R2-2108784	Work on RRM relaxation for RedCap UEs	DENSO CORPORATION
R2-2108894	Summary of [AT115-e][110][RedCap] RRM relaxation	Huawei, HiSilicon
R2-2109133	Summary of [AT115-e][110][RedCap] RRM relaxation - second round	Huawei, HiSilicon
R2-2109134	LS on RRM relaxation	Huawei
R2-2109197	LS on RRM Relaxations for RedCap	RAN2
8.13.1	Organizational
R2-2106932	LS on Area scope configuration and Frequency band info in MDT configuration (R3-212824; contact: Huawei)	RAN3
R2-2106944	Reply LS on UE context keeping in the source cell (R3-212944; contact: Ericsson)	RAN3
R2-2106946	LS on Report Amount for M4, M5, M6, M7 measurements (R3-212961; contact: Ericsson)	RAN3
R2-2106980	Reply LS on the details of logging forms reported by the gNB-CU-CP, gNB-CU-UP and gNB-DU under measurement pollution conditions (S5-213499; contact: Ericsson)	SA5
R2-2106982	LS on using SA5 Performance Measurements and Trace for centralised PCI management (S5-213689; contact: Ericsson)	SA5
R2-2107715	Using SA5 Performance Measurements and Trace for centralised PCI management	vivo
R2-2107716	[Draft] LS reply on using SA5 Performance Measurements and Trace for centralised PCI management	vivo
R2-2108310	On reply LS on Report Amount for M4, M5, M6, M7 measurements	Ericsson
R2-2108311	On reply LS to SA5 On using SA5 performance measurements and MDT for centralised PCI management	Ericsson
R2-2108966	Reply LS on on Report Amount for M4, M5, M6, M7 measurements	RAN2
R2-2108967	Reply LS on using SA5 Performance Measurements and Trace for centralised PCI management	RAN2
R2-2109050	Report of [AT115-e][891][SON/MDT] Performance Measurements and Trace for centralized PCI management (vivo)	vivo
R2-2109051	[Draft] LS reply on using SA5 Performance Measurements and Trace for centralised PCI management	vivo
R2-2109070	Report of [AT115e][890][SON/MDT] Report Amount for M4, M5, M6, M7 measurements (Ericsson)	Ericsson
8.13.2.1	Handover related SON aspects
R2-2106942	LS on UP measurements for Successful Handover Report (R3-212935; contact: Ericsson)	RAN3
R2-2107393	Further consideration of SON of HO related aspects	OPPO
R2-2107510	Further clarification on SON MRO	Nokia, Nokia Shanghai Bell
R2-2107717	Discussion on CHO, DAPS and SHR enhancements	vivo
R2-2107777	Open issues on SHR	NEC
R2-2107821	Further Discussions on CHO and DAPS Aspects	CATT
R2-2107849	Considerations on reporting successive failures in DAPS handover	LG Electronics Inc.
R2-2107883	SON Enhancements for CHO	Lenovo, Motorola Mobility
R2-2107884	SON Enhancements for DAPS Handover	Lenovo, Motorola Mobility
R2-2107885	SON Enhancements for SHR	Lenovo, Motorola Mobility
R2-2107886	SON Enhancement for NR-U	Lenovo, Motorola Mobility
R2-2108352	Consideration on CHO and DAPS related SON aspects	ZTE Corporation, Sanechips
R2-2108353	Consideration on remianing issues on SHR	ZTE Corporation, Sanechips
R2-2108417	Handover-related SON aspects	Ericsson
R2-2108419	LS Reply On user plane masurements for successful handover report	Ericsson
R2-2108425	[Post114-e][850][SON/MDT] Modeling of CHO and DAPS related RLF reports (Ericsson)	Ericsson
R2-2108430	Discussion on handover related SON aspects	Huawei, HiSilicon
R2-2108539	Remaining issues on SON Enhancement for CHO	CMCC
R2-2108540	Remaining issues on SON Enhancement for DAPS	CMCC
R2-2108541	Further Discussion on Successful Handover Report	CMCC
R2-2108564	Report of [Post114-e][851][SONMDT] Procedures and Modeling of successful HO report (Huawei)	Huawei
R2-2108570	Signalling model for CHO-related RLF report	LG Electronics Polska
R2-2108631	SON Enhancements for CHO and DAPS HO	Samsung
R2-2108766	Consideration on successful HO report	Sharp
R2-2108783	SON enhancement for DAPS	Sharp
R2-2108961	[AT115e][851][SON/MDT] CHO and DAPS related RLF reports (Ericsson)	Ericsson
R2-2108962	Report of [AT115e][852][SONMDT] Procedures and Modeling of successful HO (Huawei)	Huawei (email rapporteur)
R2-2109141	Email report of [AT115e][852][SON/MDT] Procedures and Modeling of successful HO	Huawei
8.13.2.2	2-step RA related SON aspects
R2-2107392	Discussion on 2-step RACH reporting	OPPO
R2-2107507	Remaining Issues and New Aspects in 2-step NR UE Report	Nokia, Nokia Shanghai Bell
R2-2107640	On 2-step RACH SON	Apple
R2-2107718	Discussion on remaining issues of 2-step RACH report	vivo
R2-2107822	The Remaining Issues of RACH Report for 2-step RACH	CATT
R2-2108354	2step RA related enhancements	ZTE Corporation, Sanechips
R2-2108418	2-Step RA information for SON purposes	Ericsson
R2-2108431	Discussion on 2 step RA related SON aspects	Huawei, HiSilicon
R2-2108542	SON Enhancement for 2-step RA	CMCC
R2-2108642	SON Enhancements for 2SRA	Samsung
R2-2108780	RA report for 2-step RA	Sharp
R2-2108840	Summary of 8.13.2.2 2-step RA related SON aspects	OPPO
R2-2108963	Report of [AT115e][821][SON/MDT] 2-Step RA related SON (OPPO)	OPPO
8.13.2.3	Other WID related SON features
R2-2107509	Discussion on other SON aspects	Nokia, Nokia Shanghai Bell
R2-2107511	Reporting Enhancements for SON in unlicensed access	Nokia, Nokia Shanghai Bell
R2-2107512	MPE impact on MRO	Nokia, Nokia Shanghai Bell
R2-2107823	Further Analysis on Solution of UE RACH Report for SN	CATT
R2-2107824	Further Considerations on Other SON features	CATT
R2-2107825	Report of [Post114-e][852][SON_MDT] Modeling aspects related to information required by SN/SCG	CATT
R2-2108307	On other WID related SON features	Ericsson
R2-2108334	NR-U Related Enhancements	QUALCOMM INCORPORATED
R2-2108355	On other WID related issues	ZTE Corporation, Sanechips
R2-2108432	Discussion on other WID related SON features	Huawei, HiSilicon
R2-2108643	SON Enhancements for Successful HO Report	Samsung
R2-2108648	SON Enhancements: Others	Samsung
R2-2108964	Report of [AT115e][871][SON/MDT] Modeling aspects related to information required by SN/SCG (CATT)	CATT
R2-2109208	Reply LS on RACH report for SgNB and information needed for MRO in SCG Failure Report	RAN2
8.13.3.1	Immediate MDT enhancements
R2-2107719	On RAN3 LS on MDT issues	vivo
R2-2107826	Further Considerations on Immediate MDT Enhancements	CATT
R2-2108302	On Immediate MDT Enhancements	Ericsson
R2-2108349	On accurate M5 and M7 measurements	QUALCOMM INCORPORATED
R2-2108356	Consideration on immediate MDT aspects	ZTE Corporation, Sanechips
R2-2108565	Discussion on immediate MDT enhancements	Huawei, HiSilicon
R2-2109021	Summary of 8.13.3.1 Immediate MDT enhancements	Huawei
8.13.3.2	Logged MDT enhancements
R2-2107394	logged MDT enhancement regarding RAT-specific coverage hole	OPPO
R2-2107395	Futher consideration of MDT configuration priority	OPPO
R2-2107508	Logged MDT in EN-DC and other enhancements	Nokia, Nokia Shanghai Bell
R2-2107720	On-demand SI request enhancements	vivo
R2-2107827	Considerations on MDT Enhancements for On-demand SI	CATT
R2-2108306	On logged MDT related enhancements	Ericsson
R2-2108331	Logged measurement Enhancements	QUALCOMM INCORPORATED
R2-2108357	Consideration on on-demand SI request information report	ZTE Corporation, Sanechips
R2-2108505	MDT for Slice unavailability	CMCC, Ericsson, Huawei
R2-2108543	Further consideration on UL-DL coverage mismatch	CMCC
R2-2108566	Discussion on logged MDT enhancements	Huawei, HiSilicon
R2-2108568	Discussion on Area scope configuration and Frequency band info in MDT configuration based on RAN3 LS R3-212824	Huawei, HiSilicon
R2-2108650	SON Enhancements for SI Request Optimization	Samsung
R2-2108739	Discussion on Logged MDT issues	Samsung Electronics Co., Ltd
R2-2108965	Report of [Offline-872][SONMDT] Logged MDT enhancements (Ericsson)	Ericsson
R2-2109016	[Pre115-e][811][SON/MDT] Summary of 8.13.3.2 Logged MDT enhancements (CATT)	CATT
8.13.4	L2 Measurements
R2-2107455	Discussion on the UE DL PDCP packet average delay measurement	China Telecommunication
R2-2108305	On layer-2 measurements	Ericsson
R2-2108567	Discussion on L2M	Huawei, CMCC, HiSilicon
8.14.1	Organizational
R2-2106938	LS on the mapping between service types and slice at application (R3-212904; contact: Qualcomm)	RAN3
R2-2106945	LS on requirement for configuration changes of ongoing QMC sessions (R3-212953; contact: Qualcomm)	RAN3
R2-2106949	LS on the area handling for QoE during mobility (R3-212976; contact: Qualcomm)	RAN3
R2-2108108	Running RRC CR for QoE measurements	Ericsson
R2-2108209	38.300 running CR for introduction of QoE measurements in NR	Huawei, China Unicom, HiSilicon
R2-2109004	Running RRC CR for QoE measurements	Ericsson
R2-2109005	38.300 running CR for introduction of QoE measurements in NR	Huawei, China Unicom, HiSilicon
8.14.2.1	Configuration architecture general aspects
R2-2107099	General aspects in QoE	Samsung
R2-2107380	Discussion on NR QoE configuration	CATT
R2-2107396	Further discussion on QoE measurement collection in NR	OPPO
R2-2107513	QoE handling in RAN	Nokia, Nokia Shanghai Bell
R2-2107514	RAN control on QoE reporting	Nokia, Nokia Shanghai Bell
R2-2107816	Left issues for QoE configuration and reporting	Qualcomm Incorporated
R2-2108109	Configuration and reporting of QoE measurements	Ericsson
R2-2108110	Mobility Support for NR QoE Management	Ericsson
R2-2108111	[Draft] Support for Session Start and Session End Indication	Ericsson
R2-2108197	Discussion on QoE measurement and configuration	China Unicom, China Southern Power Grid
R2-2108206	Discussion on QoE measurement configuration and reporting	Huawei, HiSilicon
R2-2108207	QoE handling during UE mobility	Huawei, HiSilicon
R2-2108227	Discussion on NR QoE configuration	ZTE Corporation, Sanechips
R2-2108228	Discussion on NR QoEcontinuity in handover	ZTE Corporation, Sanechips
R2-2108514	More considerations on configuration and reporting	CMCC
R2-2108594	Discussion on QoE measurement configuration	vivo
R2-2108595	Discussion on QoE continuity during mobility	vivo
R2-2109036	[Pre115-e][008][QoE] Summary Support for Mobility	Huawei, HiSilicon
R2-2109038	Feature summary for 8.14.2.1	Ericsson
R2-2109040	[Pre115-e][008][QoE] Summary Support for Mobility	Huawei, HiSilicon
R2-2109105	Report of offline: [AT115-e][046][QoE] Mobility (Huawei)	Huawei, HiSilicon
8.14.2.2	Start and Stop
R2-2107100	Pause and resume in QoE	Samsung
R2-2107101	Storing QoE reports in AS at pause	Samsung
R2-2107381	Activation and deactivation for QoE collection	CATT
R2-2107382	Discussion on QoE collection start and stop	CATT
R2-2107397	Discussion on QoE measurement pausing and resuming	OPPO
R2-2107515	QoE pausing	Nokia, Nokia Shanghai Bell
R2-2107615	Pause/Resume functionality	Apple
R2-2107817	Left issues for QoE pause and resume procedure	Qualcomm Incorporated
R2-2107852	Discussion on the partial QoE reporting and buffering at RAN overload	ITRI
R2-2107882	Stop and start for QoE measurement reporting	LG Electronics Inc.
R2-2108213	Discussion on pause and resume mechanism	China Unicom, China Southern Power Grid
R2-2108226	Discussion on NR QoE start and stop	ZTE Corporation, Sanechips
R2-2108515	More considerations on start and stop	CMCC
R2-2109118	Report from email discussion [AT115-e][045][QoE] QoE LS out (Ericsson)	Ericsson
R2-2109119	[Draft] QoE Reference and maximum number of QoE configurations in RRC	Ericsson
R2-2109200	QoE Reference and maximum number of QoE configurations in RRC	RAN2
8.14.3	Other
R2-2107818	Support of RAN visible QoE	Qualcomm Incorporated
R2-2108208	Initial thoughts on non-RAN2 led objectives	Huawei, HiSilicon
8.15.1	Organizational
R2-2108496	Stage 2 Running CR of TS 38.300 for eSL	InterDigital France R&D, SAS
R2-2108981	Stage 2 Running CR of TS 38.300 for eSL	InterDigital
R2-2109003	Stage 2 Running CR of TS 38.300 for eSL	InterDigital
8.15.2	SL DRX
R2-2106985	Leftover Issues for Sidelink Unicast DRX	CATT
R2-2106986	Leftover Issues for Sidelink Groupcast and Broadcast DRX	CATT
R2-2106987	Further Issues Regarding to the Tx Profile	CATT
R2-2106988	Impacts of SL DRX on Other Procedures	CATT
R2-2107041	Discussion on left issue from [704][705][706]	OPPO
R2-2107151	NR SL DRX	Fraunhofer IIS, Fraunhofer HHI
R2-2107155	Consideration on sidelink DRX for groupcast and broadcast	Huawei, HiSilicon
R2-2107156	Remaining issues on the sidelink DRX for unicast	Huawei, HiSilicon
R2-2107157	Discussion on SL communication impact on Uu DRX	Huawei, HiSilicon
R2-2107159	Summary of [POST114-e][705][V2XSL] Discussion on remaining FFSs and open issues in Uu DRX timer	Huawei, HiSilicon
R2-2107190	Left issues on SL-DRX	OPPO
R2-2107191	Discussion on SL-DRX impact to mode-1 scheduling	OPPO
R2-2107238	Leftover issues on overall flow of unicast TX-UE centric mechanism	NEC Corporation
R2-2107239	Discussion on DRX suspend/resume mechanism	NEC Corporation
R2-2107242	Further discussion on Uu/SL DRX timer	LG Electronics France
R2-2107268	Summary of [POST114-e][706][V2X/SL] Discussion on remaining FFSs/open issues in SL DRX timer maintenance (InterDigital)	InterDigital
R2-2107269	Resource Allocation Considering DRX	InterDigital
R2-2107270	Open Issues on SL DRX Timers	InterDigital
R2-2107271	DRX Configuration Determination in Unicast	InterDigital
R2-2107303	Summary of [POST114-e][704][V2X/SL] How to make sure Rel-16 UEs not supporting SL DRX are not involved in SL communication in DRX manner (Sharp)	SHARP Corporation
R2-2107310	On SL DRX Configuration aspects	Intel Corporation
R2-2107311	Discussion on SL DRX Timers	Intel Corporation
R2-2107312	On DRX wake-up time alignment	Intel Corporation
R2-2107355	Remaining issues on DRX Timers for SL Unicast	Spreadtrum Communications
R2-2107432	Consideration on Backward compatibility for SL DRX	ZTE Corporation, Sanechips
R2-2107433	Further consideration on DRX configuration	ZTE Corporation, Sanechips
R2-2107434	Discussion on SL DRX timer	ZTE Corporation, Sanechips
R2-2107472	Remaining aspects of SL DRX	Ericsson
R2-2107474	Handling coexistence between UEs supporting different releases	Ericsson
R2-2107626	Discussion on remaining issues of SL DRX configurations	Apple
R2-2107627	Discussion on remaining issues of SL impact of Uu-DRX	Apple
R2-2107653	Remaining details on HARQ RTT and Retransmission Timer for SL DRX	Fujitsu
R2-2107654	SL DRX impact on LCP	Fujitsu
R2-2107968	DRX impact on Uu	Xiaomi communications
R2-2107969	Discussion on Sidelink DRX for unicast	Xiaomi communications
R2-2107970	Discussion on Sidelink DRX for broadcast and groupcast	Xiaomi communications
R2-2108014	DRX Configuration for UC BC GC and its interaction with Sensing	Lenovo Mobile Com. Technology
R2-2108016	DRX coordination between Uu and SL	Lenovo Mobile Com. Technology
R2-2108072	Proposals for Sidelink DRX	Sony
R2-2108151	Consideration on TX centric SL DRX configuration and alignment	LG Electronics Inc.
R2-2108214	Discussion on Compatible Issues with Rel 16 UEs	Qualcomm Finland RFFE Oy
R2-2108215	Discussion on RLF and PC5 RRC Connection with SL DRX	Qualcomm Finland RFFE Oy
R2-2108217	Discussion on Remaining Issues	Qualcomm Finland RFFE Oy
R2-2108222	A Default PC5 DRX Configuration for Broadcast/Groupcast/Unicast	vivo
R2-2108223	DRX duration calculation	vivo, Xiaomi, ZTE corporation
R2-2108224	Remaining issues on SL DRX for unicast/groupcast/broadcast	vivo
R2-2108426	Discussion on TBD/FFS	Samsung Research America
R2-2108427	Further consideration for SL DRX operation in groupcast	Samsung Research America
R2-2108428	Further consideration for SL DRX and Uu DRX alignments	Samsung Research America
R2-2108469	Discussion on alignment of mode 1 RA of Tx UE and SL DRX of Rx UE	Nokia, Nokia Shanghai Bell
R2-2108470	Further Issues on Sidelink Traffic Pattern for SL DRX Configuration	Nokia, Nokia Shanghai Bell
R2-2108471	SL DRX for SL groupcast	Nokia, Nokia Shanghai Bell
R2-2108765	SL DRX enabled UE Mode 2 operation	ITL
R2-2108822	Remaining issues of SL DRX	MediaTek Inc.
R2-2108830	Left issues on SL-DRX	OPPO
R2-2108982	Summary of [AT115-e][702][V2X/SL] SL DRX configuration for UC	Ericsson
R2-2108983	Summary of [AT115-e][703][V2X/SL] SL DRX configuration for GC/BC (OPPO)	OPPO
R2-2108984	Summary of email [AT115-e][704][V2X/SL] Others	ZTE(rapporteur)
R2-2108995	LS on Tx Profile	RAN2
R2-2108997	LS to RAN1 on RAN2 Agreements Related to Resource Selection	RAN2
8.15.3	Resource allocation enhancements RAN2 scope
R2-2107042	Discussion on resource allocation enhancement	OPPO
R2-2107158	Consideration on resource allocation enhancements	Huawei, HiSilicon
R2-2107181	Power Reduction for Sidelink Mode 2 Resource Allocation	Fraunhofer IIS, Fraunhofer HHI
R2-2107182	Inter-UE Coordination for Sidelink Mode 2 Resource Allocation	Fraunhofer IIS, Fraunhofer HHI
R2-2107240	Discussion on inter-UE coordination for sidelink mode 2 resource allocation	NEC Corporation
R2-2107272	RAN2 Aspects of Inter-UE Coordination	InterDigital
R2-2107368	Discussion on resource allocation enhancement for NR sidelink	Spreadtrum Communications
R2-2107435	Discussion on inter-UE coordination	ZTE Corporation, Sanechips
R2-2107628	Discussion on Inter-UE Coordination	Apple
R2-2107629	NR SL Resource allocations for Pedestrian UEs	Apple
R2-2107918	Discussion on sidelink resource allocation enhancements	Lenovo, Motorola Mobility
R2-2107971	Resource allocation enhancement impact in RAN2	Xiaomi communications
R2-2108073	Discusison on Sidelink sensing	Sony
R2-2108118	Power efficient resource allocation and Inter-UE coordination	LG Electronics France
R2-2108191	General principles for resource allocation enhancements for SL mode 2	Ericsson
R2-2108225	Discussion on inter-UE coordination for sidelink mode2	vivo
R2-2108295	Resource Allocation Enhancements for Reduced Power Consumption and Enhanced Reliability	Intel Corporation
R2-2108429	Initial discussion on enhanced resource allocation	Samsung Research America
R2-2108472	Reduced monitoring of SL resource pools for power saving	Nokia, Nokia Shanghai Bell
R2-2108752	On Resource Allocation Mode 2 Enhancement for NR Sidelink	Convida Wireless
8.15.4	Other
R2-2107473	Interaction between partial sensing and DRX	Ericsson
R2-2107917	Discussion on backward compatible issue of SL DRX	Lenovo, Motorola Mobility
R2-2108823	SL sync search optimization	MediaTek Inc.
8.16.1	Organizational
R2-2106903	Reply LS on support of PWS over SNPN (C1-213640; contact: Qualcomm)	CT1
R2-2106934	Reply LS on support of PWS over SNPN in R17 (R3-212863; contact: Huawei)	RAN3
R2-2106983	Reply LS on support of PWS over NPN (SP-210584; contact: Qualcomm)	SA
R2-2107953	RAN2 Work Plan for Enhancement for Private Network Support for NG-RAN	Nokia, China Telecom (Rapporteurs)
R2-2107957	Draft Stage 2 CR: Non-Public Network enhancements	Nokia, Nokia Shanghai Bell
R2-2108874	Draft RRC CR: Non-Public Network enhancements	Nokia, Nokia Shanghai Bell
R2-2108980	Draft CR for Enhancements for Private Networks	Qualcomm Incorporated
8.16.2	Support SNPN with subscription or credentials by a separate entity
R2-2107029	Support SNPN with subscription or credentials by a separate entity	OPPO
R2-2107323	Further Consideration on Subscription or Credentials by CH	CATT
R2-2107458	Discussion of GIN design for NPN	China Telecommunication
R2-2107743	On Supporting Visited SNPN with Credentials	Samsung R&D Institute India
R2-2107803	Remaining issue on support SNPN by a separate entity	vivo
R2-2107954	Proposals for open issues of the support of Credential Holders	Nokia, Nokia Shanghai Bell
R2-2108046	Consideration on the Separate Entity Supporting	ZTE Corporation, Sanechips
R2-2108229	RAN2 impact to support SNPN with credentials by a separate entity	MediaTek Inc.
R2-2108254	SNPN access using external credentials	Ericsson
R2-2108545	Left Issues on Supporting SNPN with Credentials by a Separate Entity	CMCC
R2-2108612	Accessing SNPN with credentials owned by a Credentials Holder	Huawei, HiSilicon
R2-2108659	Open issues on access with external Credential Holder	LG Electronics
R2-2109033	[Pre115-e][009][eNPN] Summary 8.16.2 ext credentials + 8.16.3 onboarding (Nokia)	Nokia
8.16.3	Support UE onboarding and provisioning for NPN
R2-2107030	Support UE onboarding and provisioning for NPN	OPPO
R2-2107324	Open Issues on UE Onboarding and Provisioning for NPN	CATT
R2-2107347	UE onboarding and provisioning	Qualcomm Incorporated
R2-2107442	Remaining issues in support UE onboarding for SNPN	Intel Corporation
R2-2107744	On Supporting Onboarding SNPN	Samsung R&D Institute India
R2-2107804	Remaining issue on support UE onboarding for NPN	vivo
R2-2107955	Proposals for open issues of the support of onboarding	Nokia, Nokia Shanghai Bell
R2-2108047	Consideration on the Onboarding and Provisioning for NPN	ZTE Corporation, Sanechips
R2-2108255	UE onboarding	Ericsson
R2-2108517	Discussion the left issues to support UE on-boarding and remote provisioning	CMCC
R2-2108613	UE onboarding and remote provisioning for SNPN	Huawei, HiSilicon
R2-2108653	ASF CAG Priority	Qualcomm Incorporated
R2-2108660	Open issues for UE Onboarding	LG Electronics
8.16.4	Other
R2-2107031	Support of IMS Voice and Emergency Services for SNPN	OPPO
R2-2107325	Open Issues on Support of IMS Emergency for SNPN	CATT
R2-2107348	Support of emergency services for SNPN	Qualcomm Incorporated
R2-2107441	Support of IMS emergency call for SNPN	Intel Corporation
R2-2107752	On Supporting Emergency services in SNPNs	Samsung R&D Institute India
R2-2107805	Discussion on support of IMS voice and emergency services for SNPN	vivo
R2-2107956	Considerations for PWS and IMS emergency services in SNPNs	Nokia, Nokia Shanghai Bell
R2-2108048	Consideration on the emergency services for SNPN	ZTE Corporation, Sanechips
R2-2108256	Support of emergency services for SNPNs	Ericsson
R2-2108337	Removal of ETWS/CMAS restriction for SNPN	Qualcomm Incorporated
R2-2108342	[DRAFT] LS on introduction of PWS support over SNPN	Qualcomm Incorporated
R2-2108499	Support of emergency services for SNPN	CMCC
R2-2108614	Support of IMS voice and emergency services for SNPN	Huawei, HiSilicon
R2-2109017	[Pre115-e][010][eNPN] Summary Document for AI 8.16.4	CMCC
R2-2109113	Report from email discussion [AT115-e][050][NPN] LS out (CMCC)	CMCC
R2-2109114	LS on limited service availability of an SNPN	RAN2
8.17.1	Organizational
R2-2106936	Reply LS to RAN1 LS on TCI State Update for L1/L2-Centric Inter-Cell Mobility (R3-212879; contact: Samsung)	RAN3
R2-2106961	Reply to RAN1 LS on L1/L2-Centric Inter-Cell Mobility (R4-2108356; contact: Samsung)	RAN4
8.17.2	Support of Inter-Cell beam management
R2-2107257	Discussion on inter cell beam management	OPPO
R2-2107369	Discussion on the issue of L1L2 mobility	Spreadtrum Communications
R2-2107414	Discussion on inter-cell beam management	vivo
R2-2107415	Discussion on inter-cell MTRP operation	vivo
R2-2107554	Discussion on multi-TRP operation	Intel Corporation
R2-2107585	L1/L2-centric inter-cell beam management	Apple
R2-2107906	Discussion on support of inter-cell multi-TRP operation	Lenovo, Motorola Mobility
R2-2107948	Multi-cell support for multi-TRP	Nokia, Nokia Shanghai Bell
R2-2108005	On Inter-Cell beam management	CATT
R2-2108269	Discussion on the definition of the non-serving cell for the LS-in from RAN4 and RAN3	ZTE Corporation
R2-2108333	UL Timing Alignment for Inter-cell multi-TRP like model	DENSO CORPORATION
R2-2108442	Support of inter-cell beam management	Huawei, HiSilicon
R2-2108478	Modeling of Inter-cell mTRP	Qualcomm Incorporated
R2-2108632	Considerations on the support of inter-cell beam management	Samsung
R2-2108656	Inter-cell mTRP	LG Electronics
R2-2108761	Intial Discussion on potential RAN2 impact from Inter-cell mTRP	ZTE Corporation, Sanechips
R2-2108802	Serving cell measurement for mTRP	Xiaomi Communications
R2-2108807	On non-serving PCI related aspects of mTRP operation	Ericsson
R2-2108921	LS on inter-cell beam management and multi-TRP in Rel-17	RAN2
R2-2108925	LS on inter-cell beam management and multi-TRP in Rel-17	RAN2
R2-2109206	Report of [AT115-e][052][feMIMO] RRC modelling (Intel)	Intel Corporation
8.17.3	Other
R2-2107007	Multi TRP Beam Failure Detection and Recovery	Samsung Electronics Co., Ltd
R2-2107655	RAN2 impacts of beam failure detection and recovery	Fujitsu
R2-2107832	Discussion on RAN2 impacts of TRP-specific BFR	OPPO
R2-2107907	Beam failure recovery in multi-TRP	Lenovo, Motorola Mobility
R2-2107995	Discussion on multi-TRP BFR and new MIMO MAC CE	Qualcomm Incorporated
R2-2108246	Beam failure with mTRP	Nokia, Nokia Shanghai Bell
R2-2108443	Support of multi-TRP	Huawei, HiSilicon
R2-2108655	BFD and BFR for feMIMO	LG Electronics
R2-2108806	Overview of RAN2 impacts for BFR and BFD for mTRP operation	Ericsson
R2-2109159	Report of [AT115-e] [053] [feMIMO] Beam Failure Handling	Samsung Electronics Co., Ltd
8.18	RACH indication and partitioning
R2-2107009	Common aspects of RACH	Samsung Electronics Co., Ltd
R2-2107058	Discussion on RACH Partitioning in Rel-17	vivo
R2-2107219	Unified RACH indication and partitioning	Qualcomm Incorporated
R2-2107244	RACH partitioning common design for Rel-17 features	Beijing Xiaomi Software Tech
R2-2107256	Discussion on PRACH partitioning	OPPO
R2-2107484	RRC and MAC related aspects of common RACH configuration	ZTE Corporation, Sanechips
R2-2107552	Common aspects of RACH partitioning	Intel Corporation
R2-2107575	Cross-WI RACH Design	Apple
R2-2107835	RACH indication and partitioning	InterDigital, Europe, Ltd.
R2-2108004	On RACH indication and partitioning	CATT
R2-2108138	General aspects of RACH indication and partitioning	NEC
R2-2108210	RACH indication and partitioning	Huawei, HiSilicon
R2-2108253	RACH partitioning for Rel-17 features	Ericsson
R2-2108760	Discussion on RACH partitioning in Rel-17	LG electronics Inc.
8.19.1	Organizational
R2-2107456	Work plan for NR coverage enhancements	China Telecommunication
8.19.2	General
R2-2107008	MAC Aspects of UL Coverage Enhancements	Samsung Electronics Co., Ltd
R2-2107059	Discussion on RAN2 Impacts of Msg3 Repetition	vivo
R2-2107080	Discussion on higher layer aspects of coverage enhancements	OPPO
R2-2107220	RAN2 enhancements for Msg3 repetition	Qualcomm Incorporated
R2-2107745	Consideration on Msg3 repetition in CE	ZTE Corporation, Sanechips
R2-2108003	On support of Type A PUSCH repetitions for Msg3	CATT
R2-2108273	On RAN2 impacts for coverage enhancements and Type A PUSCH repetitions for Msg3	Ericsson
R2-2108294	RAN2 aspects of Msg3 PUSCH repetition	Intel Corporation
R2-2108604	Discussion on the support of Msg3 PUSCH repetitions	Huawei, HiSilicon
R2-2108747	Discussion on RACH with coverage enhancement	LG Electronics Inc.
R2-2108895	Summary of [AT115-e][111][CE] Msg3 repetition	ZTE Corporation
R2-2108905	[DRAFT] LS on Msg3 repetition	ZTE
R2-2109195	LS on Msg3 repetition in coverage enhancement	RAN2
8.20.1	Organizational
R2-2106917	LS on how to introduce the 52.6-71GHz frequency range (R1-2106277; contact: Lenovo)	RAN1
R2-2106954	LS on RAN4 recommendation for the 52.6 - 71 GHz frequency range designation (R4-2107879; contact: Huawei)	RAN4
R2-2108476	Workplan for Rel-17 WW Extending NR operation to 71GHz	Qualcomm Incorporated, Intel Corporation
8.20.2	General
R2-2107060	Discussion on RA(MsgB)-RNTI Design for Beyond 52.6GHz	vivo
R2-2107061	Discussion on Consistent LBT Failure Detection for Beyond 52.6GHz	vivo
R2-2107255	High layer impacts of beyond 52.6GHz	OPPO
R2-2107266	Analysis of RAN2 impacts of Ext 52-71GHz	Huawei, HiSilicon
R2-2107267	Discussion about capability issues for Ext 52-71GHz	Huawei, HiSilicon
R2-2107475	Aspects of CA operation and protocol impact	Ericsson
R2-2107476	RRC impact due to FR2-1 and FR2-2 distinction	Ericsson
R2-2107479	Impact of high SCS on RA-RNTI calculation	ZTE Corporation, Sanechips
R2-2107480	RAN2 impact for LBT for operation up to 71 GHz	ZTE Corporation, Sanechips
R2-2107551	RAN2 impact on extending NR operation to 71GHz	Intel Corporation
R2-2107792	In-device coexistence for NR above 52.6GHz	Charter Communications, Inc
R2-2107963	Discussion on RLC RTT and L2 buffer size	Samsung
R2-2107964	Impact of higher SCS on RLC operation	Samsung
R2-2107985	FR2-2 considerations	Nokia, Nokia Shanghai Bell
R2-2108477	Upper Layer impacts of extending NR operation to 71GHz	Qualcomm Incorporated
R2-2108745	Consideration on potential RACH impact	LG Electronics Inc.
R2-2108746	Consideration on potential LBT impact	LG Electronics Inc.
R2-2108858	Summary of [AT115-e][210][71 GHz] Capability differentiation between FR2-1 and FR2-2 (NN)	NN
8.21.1	TEI proposals initiated by other groups
R2-2106947	Reply LS on broadcasting gNB ID length in system information block (R3-212966; contact: Ericsson)	RAN3
R2-2108298	[gNB_ID_Length] On the inclusion of gNB ID length in the NR CGI report	Ericsson
R2-2108300	[gNB_ID_Length] On the inclusion of gNB ID length in the NR CGI report	Ericsson
R2-2108301	[gNB_ID_Length] On the inclusion of gNB ID length in the NR CGI report	Ericsson
R2-2108303	On broadcasting gNB ID length in system information block and associated CGI reporting (reply to RAN3 LS R3-212966)	Ericsson
R2-2108313	[Draft] Reply LS on broadcasting gNB ID length in system information block	Ericsson
R2-2108409	NR positioning support for TA-based positioning in E-CID (TEI)	Ericsson
R2-2108640	Discussion on broadcasting gNB ID length in system information block	Huawei, HiSilicon
8.21.2	TEI proposals initiated by RAN2
R2-2108408	On the need of providing explicit SI start position for SI Scheduling	Ericsson
8.21.2.1	CP centric
R2-2107023	UE assistance information configuration in RRCResume message	OPPO
R2-2107024	Security algorithms update in RRC reestablishment message	OPPO
R2-2107259	Discussion on Idle/Inactive Measurement for Load Distribution	NTT DOCOMO INC.
R2-2107637	User preferences to control location information sharing	Apple, Samsung, Google, Xiaomi, Mediatek, Vivo
R2-2107815	User Plane Integrity Protection	Nokia, Nokia Shanghai Bell
R2-2108130	Specification release filtering for NR UE capabilities	Huawei, HiSilicon
R2-2108347	Improved granularity for the number of PDSCH HARQ processes	Nokia, Nokia Shanghai Bell
R2-2108403	RRC processing delay for DL RRC segmentation	Ericsson
R2-2108501	Mobility-state-based cell reselection to support NR High Speed railway Dedicated Network (HSDN)	CMCC, CATT, Ericsson, Huawei, ZTE, OPPO, vivo
R2-2108502	38.331 CR to introduce mobility-state-based cell reselection for NR HSDN	CMCC, CATT, Ericsson, Huawei, ZTE, OPPO, vivo
R2-2108503	38.304 CR to introduce mobility-state-based cell reselection for NR HSDN	CMCC, CATT, Ericsson, Huawei, ZTE, OPPO, vivo
R2-2108670	Reduce the blind redirection for EPS Fallback	vivo, China Telecom, CMCC, China Unicom
R2-2108696	Common Cell Configuration for Signaling Reduction in NR	CATT, Verizon, CMCC, Huawei, HiSilicon
R2-2108805	On the need of providing explicit SI start position for SI Scheduling	Ericsson, Verizon
R2-2108814	On the support of NG-based handover using CGI report	Huawei, HiSilicon, CMCC, China Telecom, China Unicom
R2-2109034	Common Cell Configuration for Signaling Reduction in NR	CATT, Verizon, CMCC, Huawei, HiSilicon, Samsung
R2-2109044	User preferences to control location information sharing	Apple, Samsung, Google, Xiaomi, Mediatek, Vivo, BT
8.21.2.2	UP centric
R2-2107221	C-DRX enhancement for XR/CG applications	Qualcomm Incorporated, Verizon Wireless, Facebook
R2-2107416	C-DRX enhancements for 5G applications	vivo, CMCC, China Telecom, Guangdong Genius, Spreadtrum, China Unicom
R2-2107542	Adaptation of QoS Flow to DRB Mapping for MDBV Enforcement	Futurewei
R2-2107543	Activation/Deactivation of QoS Flow to DRB Mapping for SMBR Enforcement	Futurewei
R2-2108233	Enhanced DRX inactivity timer operation for UE power saving	MediaTek Inc.
R2-2108720	UE assistance information for UL pre-scheduling	MediaTek Inc.
R2-2108850	C-DRX enhancement for XR/CG applications	Qualcomm Incorporated, Verizon Wireless, Facebook, MediaTek
R2-2109019	Enhanced DRX inactivity timer operation for UE power saving	MediaTek Inc., Qualcomm
R2-2109020	UE assistance information for UL pre-scheduling	MediaTek Inc., Qualcomm
8.22	NR R17 Other
R2-2106902	LS on UAC enhancements for minimization of service interruption when disaster condition applies (C1-213527; contact: Nokia)	CT1
R2-2106907	Reply LS on Rel-17 uplink Tx switching (R1-2104137; contact: China Telecom)	RAN1
R2-2106910	LS response on New Standardized 5QIs for 5G-AIS (Advanced Interactive Services) (R1-2106149; contact: Qualcomm)	RAN1
R2-2106927	Reply LS to CT4 on Information on the port number allocation solutions (R3-212800; contact: Huawei)	RAN3
R2-2106939	Response LS on Handover terminology (R3-212907; contact: Nokia)	RAN3
R2-2106951	LS on Rel-17 Tx switching enhancements (R4-2103234; contact: China Telecom)	RAN4
R2-2106953	Reply LS on Rel-17 uplink Tx switching (R4-2107847; contact: China Telecom)	RAN4
R2-2106957	LS on NR CA capability for BCS5 (R4-2108002; contact: Xiaomi)	RAN4
R2-2106965	Reply LS to SA4 on UE Data Collection (S2-2104864; contact: Qualcomm)	SA2
R2-2106974	Reply LS to LS on broadcasting from other PLMN in case of Disaster Condition (S3-212258; contact: LGE)	SA3
R2-2106977	LS on security protection on RRCResumeRequest message (S3-212349; contact: Apple)	SA3
R2-2106978	Reply LS to SA2 on UE Data Collection (S4-210961; contact: Qualcomm)	SA4
R2-2107126	Introduction of BCS4 and BCS5	Qualcomm Incorporated, Nokia, Nokia Shanghai Bell
R2-2107127	Introduction of supported minimum bandwidth per CC for BCS5	Qualcomm Incorporated, Nokia, Nokia Shanghai Bell
R2-2107128	Introduction of supported minimum bandwidth per CC for BCS5	Qualcomm Incorporated, Nokia, Nokia Shanghai Bell
R2-2107183	Discussion on BCS5	OPPO
R2-2107184	Discussion on UAC for service interruption minimization during disaster	OPPO
R2-2107264	Discussion of the MINT solutions #38 and #40	Lenovo, Motorola Mobility
R2-2107299	Discussion and Response on SA3 LS on new ResumeMac-I calculation	Intel Corporation
R2-2107417	Discussion on capability of supporting txDiversity	vivo
R2-2107483	On the security protection of RRCResumeRequest message	ZTE Corporation, Sanechips
R2-2107572	DRAFT LS Reply on security protection on RRCResumeRequest message	Apple [To be RAN2]
R2-2107574	The security protection on RRCResumeRequest	Apple Inc, Ericsson Inc
R2-2107590	Discussion on UAC enhancement for MINT	Apple
R2-2107591	Discussion on Rel-17 UL Tx Switching	Apple
R2-2107840	Draft LS reply on UAC enhancements for minimization of service interruption when disaster condition applies	vivo
R2-2107841	UAC enhancements for minimization of service interruption when disaster condition applies	vivo
R2-2107842	Draft LS reply on security protection on RRCResumeRequest message	vivo
R2-2107843	Security protection on RRCResumeRequest message	vivo
R2-2107979	UE capabilities for UL Tx switching enhancement	Ericsson
R2-2108041	CR on the BCS4/5 supporting-38331	ZTE Corporation, Sanechips
R2-2108042	CR on the BCS4/5 supporting-38306	ZTE Corporation, Sanechips
R2-2108043	Consideration on the BCS4/5 supporting	ZTE Corporation, Sanechips
R2-2108044	CR on the BCS4 supporting-r15	ZTE Corporation, Sanechips
R2-2108045	CR on the BCS4 supporting-r16	ZTE Corporation, Sanechips
R2-2108158	RAN2 impact to support R17 UL Tx switching enhancement	Huawei, HiSilicon, Apple
R2-2108159	Draft CR to TS38.331 to support Tx switching enhancements	Huawei, HiSilicon, China Telecom, Apple, CATT
R2-2108160	Draft CR to TS38.306 to support Tx switching enhancements	Huawei, HiSilicon, China Telecom, Apple, CATT
R2-2108216	Extended MAC-I for RRCResumeRequest	MediaTek Inc.
R2-2108274	UE capability reporting and RRC configuration for Rel-17 UL Tx switching enhancements	China Telecommunication, CATT, Baicells
R2-2108348	Discussion on security enhancement for RRCResumeRequest	Xiaomi Communications
R2-2108366	RAN2 aspects for MINT	Ericsson
R2-2108537	CR on 38.331 for introducing UE capability of txDiversity	CMCC
R2-2108538	CR on 38.306 for introducing UE capability of txDiversity	CMCC
R2-2108588	Discussion on transparent TxD capability signalling	Huawei, HiSilicon, CMCC
R2-2108589	Discussion on the signalling for BCS5	Huawei, HiSilicon
R2-2108620	Considerations on cross-carrier scheduling from SCell to P(S)Cell	Huawei, HiSilicon
R2-2108621	Security protection on RRCResumeRequest message	Huawei, HiSilicon
R2-2108633	Considerations on the UAC enhancements when disaster condition applies	Samsung
R2-2108639	Discussion on on UAC enhancements for minimization of service interruption when disaster condition applies	Huawei, HiSilicon
R2-2108671	R17 TX switching enhancements	vivo
R2-2108672	CR to 38.331 on Rel-17 Tx switching enhancements	vivo
R2-2108673	CR to 38.306 on Rel-17 Tx switching enhancements	vivo
R2-2108762	UAC for minimization of service interruption when disaster condition applies	ZTE corporation, Sanechips
R2-2108763	draft reply LS on UAC enhancements for minimization of service interruption when disaster condition applies	ZTE corporation, Sanechips
R2-2108801	NR CA capability for BCS5	Xiaomi Communications
R2-2108818	Draft reply LS to CT1 on UAC extensions for MINT (R2-2106902/C1-213527)	Nokia Poland
R2-2109042	Summary of [AT115-e][035][NR17] TX switching (China Telecom)	China Telecommunications
R2-2109054	[AT115-e][032][NR17] Security protection RRC Resume (Apple)	Apple
R2-2109058	Report of email discussion [AT115-e][031][NR17] MINT	Nokia
R2-2109060	DRAFT LS Reply on security protection on RRCResumeRequest message	Apple [To be RAN2]
R2-2109073	Reply LS for NR CA capability for BCS5	RAN2
R2-2109088	Draft CR to TS38.331 to support Tx switching enhancements	Huawei, HiSilicon, China Telecom, Apple, CATT
R2-2109089	Draft CR to TS38.306 to support Tx switching enhancements	Huawei, HiSilicon, China Telecom, Apple, CATT
R2-2109101	Band n77 issues in the US – Comparison of solutions	Ericsson
R2-2109120	New band number for n77 DoD	Ericsson
R2-2109121	LS Reply to SA3 on security protection on RRCResumeRequest message	RAN2
R2-2109142	The report of [AT115-e][034][NR17] TX diversity (CMCC)	CMCC (Rapporteur)
R2-2109173	Reply LS on UAC enhancements for minimization of service interruption when disaster condition applies	RAN2
R2-2109224	Summary of [AT115-e][035][NR17] TX switching (China Telecom)	China Telecommunications
R2-2109225	Running CR to TS38.331 to support Tx switching enhancements	Huawei, HiSilicon, China Telecom, Apple, CATT
R2-2109226	Running CR to TS38.306 to support Tx switching enhancements	Huawei, HiSilicon, China Telecom, Apple, CATT
9.1.1	Organizational
R2-2108974	RAN2 agreements for Rel-17 NB-IoT and LTE-MTC	Document Rapporteur (Ericsson)
9.1.2	NB-IoT neighbor cell measurements and corresponding measurement triggering before RLF
R2-2107122	Consideration on neighbour cell measurement in RRC connected state	Qualcomm Incorporated
R2-2107429	Open issues on connected mode measurements for RLF	Huawei, HiSilicon
R2-2107761	Remaining issues on connected mode measurement	ZTE Corporation, Sanechips
R2-2107810	Network assistance information for Re-establishment time reduction	Nokia, Nokia Shanghai Bell
R2-2107811	On the open aspects for connected mode measurements for RLF enhancements	Nokia, Nokia Shanghai Bell
R2-2107869	Triggering cell selection early	Huawei, HiSilicon, MediaTek Inc., Spreadtrum Communications, Lenovo, Motorola Mobility, Fraunhofer, Novamint, CMCC, China Unicom, Reliance Jio
R2-2108390	Discussion on connected mode measurement in NB-IoT	Ericsson
R2-2108843	Summary of AI 9.1.2 NB-IoT neighbor cell measurements (Huawei)	Huawei
R2-2108971	Summary of [301] RLF measurements (Huawei)	Huawei
9.1.3	NB-IoT carrier selection based on the coverage level, and associated carrier specific configuration
R2-2107123	Support for NB-IoT carrier selection based on the coverage level	Qualcomm Incorporated
R2-2107124	Signalling for coverage-based paging carrier selection	Qualcomm Incorporated
R2-2107207	Discussion on details of paging carrier selection options	MediaTek Inc.
R2-2107370	Further discussion on enhanced paging carrier selection	Spreadtrum Communications
R2-2107391	Further discussion on enhanced paging carrier selection	NEC Corporation
R2-2107430	Paging carrier selection	Huawei, HiSilicon
R2-2107762	Remaining issues on CEL-based paging carrier selection	ZTE Corporation, Sanechips
R2-2107812	Further analysis on solution for coverage level based paging carrier selection	Nokia, Nokia Shanghai Bell
R2-2108391	Paging Carrier Selection	Ericsson
R2-2108828	Summary of AI 9.1.3 NB-IoT carrier selection	Ericsson
R2-2108972	[AT115-e][302][NBIOT/eMTC R17] carrier selection (Ericsson)	Ericsson
9.1.4	Other
R2-2107431	L2 buffer size calculations for eMTC and NB-IoT enhancements	Huawei, HiSilicon
R2-2107763	Remaining issues on 14 HARQ and 1736bits TBS for eMTC	ZTE Corporation, Sanechips
R2-2107764	Remaining issues on 16QAM for NB-IoT	ZTE Corporation, Sanechips
R2-2107996	Report of [AT114-e][302][NBIOT/eMTC R17] NB-IoT/eMTC Other	ZTE (email discussion rapporteur)
R2-2108392	Support of 16-QAM for unicast in UL and DL in NB-IoT	Ericsson
R2-2108742	Total L2 Buffer Size for NB-IoT and LTE-M UEs	Ericsson
R2-2108973	Summary of AI 9.1.4 NB-IoT/eMTC Other-Phase 2 (ZTE)	ZTE (email discussion rapporteur)
R2-2109030	[Pre115-e][303][NBIOT/eMTC R17] Summary of AI 9.1.4 Other (ZTE)	ZTE Corporation
9.2.1	Organizational
R2-2106929	Reply LS to LS on IoT-NTN basic architecture (R3-212806; contact: Qualcomm)	RAN3
R2-2108849	LTE_NBIOT_eMTC_NTN work plan	MediaTek, Eutelsat
R2-2108922	Running CR - Support of Non-Terrestrial Network in NB-IoT and eMTC	Huawei
R2-2108975	Idle mode 36304 Running CR for IoT NTN	Ericsson
R2-2108976	Stage-3 running CR for TS 36.321 for Rel-17 IoT-NTN	MediaTek
R2-2108977	NB-IoT/eMTC support for Non-Terrestrial Networks [Stage 2 Running CR]	Eutelsat S.A.
9.2.2	Support of Non continuous coverage
R2-2107081	Discussion on the support of discontinuous coverage for IoT over NTN	OPPO
R2-2107319	Discussion on discontinuous coverage	CATT
R2-2107400	UE behavior for Discontinuous coverage in NTN IoT	Rakuten Mobile, Inc
R2-2107424	Discussion on non continuous coverage	Huawei, HiSilicon
R2-2107453	On LEO satellite flyover timing and discontinuous coverage	Eutelsat S.A.
R2-2107559	Support of non-continuous coverage	Qualcomm Incorporated
R2-2107613	Support of discontinuous coverage	Apple
R2-2107765	Support of discontinuous coverage in IoT NTN	ZTE Corporation, Sanechips
R2-2107913	Enhancement for idle UE power saving in discontinuous coverage	Lenovo, Motorola Mobility
R2-2107914	RRC connection handling for discontinuous coverage in IoT NTN	Lenovo, Motorola Mobility
R2-2108116	On support of Non continuous coverage	Nokia, Nokia Shanghai Bell
R2-2108171	Discussion on discontinuous coverage	Xiaomi
R2-2108325	Support of discontinuous coverage	NEC Telecom MODUS Ltd.
R2-2108336	On Discontinuous coverage in IoT-NTN	MediaTek Inc.
R2-2108500	Discussion on support of Non continuous coverage	CMCC
R2-2108740	Discontinuous coverage in IoT NTN	Ericsson
R2-2109059	Summary of 9.2.2 Non continuous coverage	MediaTek Inc.
R2-2109152	LS on supporting discontinuous coverage in IoT NTN	RAN2
R2-2109201	[draft] LS on supporting discontinuous coverage in IoT NTN	MediaTek
R2-2109213	LS on supporting discontinuous coverage in IoT NTN	RAN2
9.2.3	User Plane Impact
R2-2107082	Discussion on UP impact for IoT over NTN	OPPO
R2-2107320	User Plane Impact for IOT NTN	CATT
R2-2107425	User plane for IOT NTN	Huawei, HiSilicon
R2-2107614	Provision of ephemeris	Apple
R2-2107766	User plane aspects of IoT NTN	ZTE Corporation, Sanechips
R2-2107915	Further enhancement for PUR in IoT NTN	Lenovo, Motorola Mobility
R2-2108117	Discussion on User Plane impact for IoT NTN	Nokia, Nokia Shanghai Bell
R2-2108335	On User-Plane Timers in NB-IoT based NTN	MediaTek Inc.
R2-2108454	User plane aspects of NB-IoT and LTE-M in NTNs	Ericsson
R2-2108529	User plane for IoT-NTN	CMCC
R2-2109043	Summary of [AT115-e][037][IoT-NTN] User Plane Impact (OPPO)	OPPO
9.2.4.1	TA and Mobility related
R2-2107083	Discussion on CP impact for IoT over NTN	OPPO
R2-2107084	Discussion on idle mode procedures for IoT over NTN	OPPO
R2-2107321	Discussion on connected mode UE of IoT NTN	CATT
R2-2107322	Discussion on IDLE mode UE of IoT NTN	CATT
R2-2107371	Discussion on the issue of mobility for IoT over NTN	Spreadtrum Communications
R2-2107426	TA and mobility for IOT NTN	Huawei, HiSilicon
R2-2107562	TAC update procedure	Qualcomm Incorporated
R2-2107767	Mobility issues of IoT NTN	ZTE Corporation, Sanechips
R2-2107813	Analysis on mobility aspects for IoT-NTN	Nokia, Nokia Shanghai Bell
R2-2107916	Considerations on NB-IoT mobility for IoT NTN	Lenovo, Motorola Mobility
R2-2108018	Discussion on connected mode mobility for IoT NTN	Xiaomi Communications
R2-2108172	Discussion on TA and idle mode mobility enhancement	Xiaomi
R2-2108328	Mobility enhancement for IoT-NTN	NEC Telecom MODUS Ltd.
R2-2108338	On Cell Re-selection in IoT-NTN	MediaTek Inc.
R2-2108339	On Improving Tracking Area Updates in IoT NTN	MediaTek Inc.
R2-2108546	Enhanced RRC re-establishment for mobility in IoT-NTN	CMCC
R2-2108548	Discussion on TA Update for IoT-NTN	CMCC
R2-2108757	Mobility for NB-IoT and LTE-M in NTN	Ericsson
R2-2108915	RRM impact for supporting CHO in IoT NTN	RAN2
R2-2109093	Summary of AI 9.2.4.1 “TA and Mobility related” (Ericsson)	Ericsson
R2-2109176	Summary of AI 9.2.4.1 “TA and Mobility related” (Ericsson)	Ericsson
9.2.4.2	Other
R2-2107427	Control plane - Other for IOT NTN	Huawei, HiSilicon
R2-2107560	Recovery of synchronization in RRC_CONNECTED	Qualcomm Incorporated
R2-2107561	UL synchronization and Paging response delay	Qualcomm Incorporated
R2-2107768	Other control plane aspects of IoT NTN	ZTE Corporation, Sanechips
R2-2107814	On Paging and idle mode cell reselection enhancements for IoT-NTN	Nokia, Nokia Shanghai Bell
R2-2107988	Consideration on RRC release for IOT NTN	Beijing Xiaomi Mobile Software
R2-2108750	SIB acquisition during cell reselection in IoT NTN	Ericsson
9.3	EUTRA R17 Other
R2-2106930	Reply LS to LS on User Plane Integrity Protection for eUTRA connected to EPC (R3-212812; contact: Qualcomm)	RAN3
R2-2107125	UE specific DRX during EDT	Qualcomm Incorporated
R2-2107214	Introduction of event-based trigger for LTE MDT logging	KDDI Corporation, CMCC, Telecom Italia, Samsung, Ericsson
R2-2107215	Introduction of event-based trigger for LTE MDT logging	KDDI Corporation, CMCC, Telecom Italia, Samsung, Ericsson
R2-2107225	Introduction of sensor-LocationInfo for LTE MDT	KDDI Corporation
R2-2107589	Adding NR-U RSSI/CO measurement UE capability into LTE	Apple
R2-2108556	Discussion on event triggered logged MDT for LTE	Huawei, HiSilicon
R2-2108557	CR to 36.306 on event triggered logged MDT for LTE	Huawei, HiSilicon
R2-2108558	CR to 36.331 on event triggered logged MDT for LTE	Huawei, HiSilicon
R2-2108559	CR to 37.320 on event triggered logged MDT for LTE	Huawei, HiSilicon
R2-2108560	CR to 36.304 on event triggered logged MDT for LTE	Huawei, HiSilicon
R2-2108596	Introduction of sensor-LocationInfo for LTE MDT	KDDI Corporation
R2-2109027	Introduction of event-based trigger for LTE MDT logging	KDDI Corporation, CMCC, Telecom Italia, Samsung, Ericsson, China Unicom
R2-2109028	Introduction of event-based trigger for LTE MDT logging	KDDI Corporation, CMCC, Telecom Italia, Samsung, Ericsson, China Unicom
9.4	NR and EUTRA Inclusive language
R2-2106981	LS on Inclusive language for ANR (S5-213683; contact: Ericsson)	SA5
R2-2108297	Inclusive Language Review Status and Consistency Check	Ericsson (coordinator)
R2-2108853	Reply LS on Inclusive language for ANR	Ericsson
R2-2108869	Reply LS on Inclusive language for ANR	RAN2
10.1	Session on LTE legacy, Mobility, DCCA, Multi-SIM and RAN slicing
R2-2108831	Report from session on LTE legacy, 71 GHz, DCCA, Multi-SIM and RAN slicing	Vice Chairman (Nokia)
10.2	Session on R17 NTN and RedCap
R2-2108832	Report from Break-Out Session on R17 NTN, RedCap and CE	Vice Chairman (ZTE)
10.3	Session on eMTC
R2-2108833	Report eMTC breakout session	Session chair (Ericsson)
10.4	Session on R17 Small data and URLLC/IIOT
R2-2108834	Report for Rel-17 Small data and URLLC/IIoT	Session chair (InterDigital)
10.5	Session on positioning and sidelink relay
R2-2108835	Report from session on positioning and sidelink relay	Session chair (MediaTek)
10.6	Session on SON/MDT
R2-2108836	Report from SOM/MDT session	Session chair (CMCC)
10.7	Session on NB-IoT
R2-2108837	Report NB-IoT breakout session	Session chair (Huawei)
10.8	Session on LTE V2X and NR SL
R2-2108838	Report from session on LTE V2X and NR SL	Session chair (Samsung)